View AT86RF230-ZU_2087161.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

1 5131e-mcu wireless-02/09 at86rf230 features ? high performance rf-cmos 2.4 ghz ra dio transceiver targeted for ieee 802.15.4?, zigbee ? , 6lowpan, rf4ce, sp100, wirelesshart? and ism applications ? industry leading link budget (104 db): - programmable output power from -17 dbm up to 3 dbm - receiver sensitivity -101 dbm ? ultra-low power consumption: - sleep: 20 na - rx: 15.5 ma - tx: 16.5 ma (at max transmit power of 3 dbm) ? ultra-low supply voltage (1.8v to 3.6v) with internal regulator ? optimized for low bom cost and ease of production: - few external components necessary (crystal, capacitors and antenna) ? excellent esd robustness ? easy to use interface: - registers and frame buffer accessible through fast spi - only two microcontroller gpio lines necessary - one interrupt pin from radio transceiver - clock output with prescaler from radio transceiver ? radio transceiver features: - 128-byte sram for data buffering - programmable clock output to clock the host microcontroller or as timer reference - integrated tx/rx switch - fully integrated pll with on-chip loop filter - fast pll settling time - battery monitor - fast power-up time < 1 ms ? special ieee 802.15.4-2003 hardware support: - fcs computation - clear channel assessment - energy detection / rssi computation - automatic csma-ca - automatic frame retransmission - automatic frame acknowledgement - automatic address filtering ? industrial temperature range: - -40 c to 85 c ? i/o and packages: - 32-pin low-profile qfn - rohs/fully green ? compliant to en 300 328/440, fcc-cfr-47 part 15, arib std-66, rss-210 ? compliant to ieee 802.15.4-2003 low power 2.4 ghz transceiver for zigbee, ieee 802.15.4, 6lowpan, rf4ce and ism applications at86rf230 5131e-mcu wireless-02/09
2 5131e-mcu wireless-02/09 at86rf230 1 pin-out diagram figure 1-1. at86rf230 pin-out diagram avss avss avss rfp rfn avss tst irq mosi dvss miso sclk dvss clkm avss avss avss avdd evdd avss xtal2 xtal1 dvss dvss slp_tr dvss dvdd dvdd devdd dvss 32 31 30 29 28 27 26 25 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 24 23 22 21 20 19 18 17 at86rf230 rst sel avss exposed paddle note: the exposed paddle is electrically connected to the die inside the package. it shall be soldered to the board to ensure electrical and thermal contact and good mechanical stability. disclaimer typical values contained in this datasheet are based on simulations and testing. min and max values will be available when the radio transceiver has been fully characterized. 2 overview the at86rf230 is a low-power 2.4 ghz radio transceiver especially designed for zigbee/ieee 802.15.4 applications. the at86rf 230 is a true spi-t o-antenna solution. all rf-critical components except the antenna, crystal and de-coupling capacitors are integrated on-chip. therefore, the at86rf230 is particularly suitable for applications like: ? 2.4 ghz ieee 802.15.4 and zigbee systems ? 6lowpan and rf4ce systems ? wireless sensor networks ? industrial control, sensing and automation (sp100, wirelesshart) ? home and building automation ? consumer electronics ? pc peripherals the at86rf230 can be operated by using an external microcontroller like atmel?s avr microcontrollers. a comprehensive so ftware programming description can be found in the application note avr2009 ?a t86rf230 ? software programming model?.
3 5131e-mcu wireless-02/09 at86rf230 3 general circuit description this single-chip radio transceiver provides a complete radio transceiver interface between the antenna and the microcontroller. it comprises the analog radio transceiver and the digital demodulation including time and frequency synchronization, and data buffering. the number of external components is minimized such that only an antenna, a crystal and four decoupling capacitors are required. the bidirectional differential antenna pins are used for transmission and reception, so that no external antenna switch is needed. the at86rf230 block diagram is shown in figure 3-1. figure 3-1. block diagram of the at86rf230 lna ppf adc agc pa frequency synthesis i q spi slave interface tx power control tx data limiter 5 rssi xosc control logic/ configuration registers clkm xtal1 xtal2 fame buffer tx bbp rx bbp ssbf irq sclk miso mosi slp_tr dclk rfp rfn digital domain analog domain dvreg batmon avreg ftn rst sel the received rf signal at pins rfn and rf p is differentially fed through the low-noise amplifier (lna) to the rf filter (ppf) to generate a complex signal. this signal is converted down by mixers to an intermediate frequency and fed to the integrated channel filter (ssbf). the limiting amplif ier provides sufficient gain to drive the succeeding analog-to-digital conv erter (adc) and generates a digital rssi signal with 3 db granularity. the adc output signal is sampled by the digital base band receiver (rx bbp). the transmit modulation scheme is offset-q psk (o-qpsk) with half -sine pulse shaping and 32-length block coding (spreading) according to [1]. the modulation signal is generated in the digital transmitter (tx bbp) and applied to the fractional-n frequency synthesis (pll) generating a coherent phase modulation required for demodulation of o-qpsk signals. the frequency-modulated rf signal is fed to the power amplifier (pa). an internal 128 byte ram for rx and tx (frame buffer) buffers the data to be transmitted or the received data. two on ch ip low dropout (ldo) voltage regulators provide the internal analog and digital 1.8v supply.
4 5131e-mcu wireless-02/09 at86rf230 4 pin description table 4-1. at86rf230 pin list number name type description 1 avss ground analog ground 2 avss ground analog ground 3 avss ground ground for rf signals 4 rfp rf i/o differential rf signal 5 rfn rf i/o differential rf signal 6 avss ground ground for rf signals 7 tst digital input enables continuous transmission test mode; active high 8 rst digital input chip reset; active low 9 dvss ground digital ground 10 dvss ground digital ground 11 slp_tr digital input controls sleep, tr ansmit start and receive states; active high 12 dvss ground digital ground 13 dvdd supply regulated 1.8v supply voltage; digital domain 14 dvdd supply regulated 1.8v supply voltage; digital domain 15 devdd supply external supply voltage; digital domain 16 dvss ground digital ground 17 clkm digital output master clock signal output 18 dvss ground digital ground 19 sclk digital input spi clock 20 miso digital output spi data out put (master input slave output) 21 dvss ground digital ground 22 mosi digital input spi data in put (master output slave input) 23 sel digital input spi select; active low 24 irq digital output interrupt request signal; active high 25 xtal1 analog input crystal pin or external clock supply 26 xtal2 analog input crystal pin 27 avss ground analog ground 28 evdd supply external supply voltage; analog domain 29 avdd supply regulated 1.8v supply voltage; analog domain 30 avss ground analog ground 31 avss ground analog ground 32 avss ground analog ground paddle avss ground analog ground; exposed paddle of qfn package 4.1 supply and ground pins evdd, devdd evdd and devdd are analog and digital suppl y voltage pins of the at86rf230 radio transceiver.
5 5131e-mcu wireless-02/09 at86rf230 avdd, dvdd avdd and dvdd are outputs of the internal 1.8v voltage regulators. the voltage regulators are controlled independently by t he radio transceivers state machine and are activated depending on the current radio tr ansceiver state. the voltage regulators can be configured for external supply. for details refer to section 9.4. avss, dvss avss and dvss are analog and digital ground pins respectively. the analog and digital power domains should be separated on the pcb, for further details see application note avr2005 "design considerations for the at86rf230". 4.2 analog and rf pins rfp, rfn a differential rf port (rfp/rfn) provides common-mode rejection to suppress the switching noise of the internal digital signal processing blocks. at the board-level, the differential rf layout ensures high receiv er sensitivity by rejecting any spurious interspersions originating from other digital ics such as a microcontroller. the rf port is designed for a 100 ? differential load. a dc path between the rf pins is allowed. a dc path to ground or supply voltage is not allowed. therefore, when connecting a rf-load providing a dc path to the power supply or to ground, capacitive coupling is required as indicated in table 4-2. a simplified schem atic of the rf front end is shown in figure 4-1. figure 4-1. simplified rf front-end schematic lna pa rfp rfn rxtx 0.9v tx rx cm feedback m0 at86rf230 pcb rf port dc values depend on the operating mode. in trx_off state (see section 7.1.2), when the analog front end is disabled, the rf pins are pulled to ground, preventin g a floating voltage.
6 5131e-mcu wireless-02/09 at86rf230 in receive mode, the rf input provides a low-impedance path to ground when transistor m0 (see figure 4-1) pulls the inductor center ta p to ground. a dc voltage drop of 20 mv across the on-chip inductor can be measured at the rf pins. in transmit mode, a control loop provides a common-mode voltage of 0.9v. transistor m0 is off, allowing the pa to set the common-mode voltage. the common-mode capacitance at each pin to ground shall be < 30 pf to ensure the stability of this common-mode feedback loop. xtal1, xtal2 the pin xtal1 is the input of the reference oscillator amplifier (xosc), xtal2 is the output. a detailed description of the crystal oscillator setup and the related xtal1/xtal2 pin configurat ion can be found in section 9.6. whe n using an external clock reference signal, xtal1 shall be used as input pin. for further details refer to section 9.6.3. table 4-2. comments on analog and rf pins pin condition recommendation/comment rfp/rfn vdc = 0.9v (tx) vdc = 20 mv (rx) at both pins ac-coupling is required if an antenn a with a dc path to ground is used. serial capacitance must be < 30 pf. xtal1/xtal2 cpar = 3 pf vdc = 0.9v at both pins parasitic capacitance (cpar) of the pi ns must be considered as additional load capacitance to the crystal. 4.3 digital pins the digital interface of the at86rf230 compromises pins sel , sclk, mosi and miso forming the serial peripheral interface (spi) and pins clkm, irq, slp_tr and rst used as additional control signal bet ween radio transceiver and microcontroller. the digital radio transceiver interface is described in detail in section 6. 4.3.1 driver strength settings of digital ou tput pins the driver strength of the digital output pins (miso, irq) and clkm pin can be configured by register 0x03 (trx_ctrl_0) as described in table 4-3. the capa citive load should be as small as possible and not larger than 50 pf when using the 2 ma minimum driver strength setti ng. generally, the output driver strength should be adjusted to the lowest possible value in order to keep the current consumption and the emission of digital signal harmonics low. table 4-3. digital output driver configuration pin default driver strength comment miso, irq 2 ma adjustable to 2 ma, 4 ma, 6 ma and 8 ma clkm 4 ma adjustable to 2 ma, 4 ma, 6 ma and 8 ma
7 5131e-mcu wireless-02/09 at86rf230 4.3.2 pull-up and pull-down configuration of digital input pins pulling resistors are internally connected to all digital input pins in radio transceiver state p_on (see section 7.1.2). table 4-4 summarizes the pull-up and pull-down config uration. table 4-4 pull-up/pull-down configuration of digital input pins in p_on state pin h ? pull-up, l ? pull-down rst h sel h sclk l mosi l slp_tr l in all other radio transceiver states, no pull- up or pull-down resistors are connected to any of the digital input pins. 4.3.3 register description regis ter 0x03 (trx_ctrl_0) the trx_ctrl_0 register controls the driv e current of the digital output pads and the clkm clock rate. bit 7 6 5 4 0x03 pad_io pad_io_clkm trx_ctrl_0 read/write r/w r/w r/w r/w reset value 0 0 0 1 bit 3 2 1 0 0x03 clkm_sha_sel clkm_ctrl trx_ctrl_0 read/write r/w r/w r/w r/w reset value 1 0 0 1 x bit [7:6] ? pad_io the register bits pad_io set the output driver current of digital output pads miso and irq. table 4-5. digital output driver strength register bit value description 0 (1) 2 ma 1 4 ma 2 6 ma pad_io 3 8 ma notes: 1. reset values of register bits are underlined characterized in the document. x bit [5:6] ? pad_io_clkm the register bits pad_io_clkm set the output driver current of pin clkm.
8 5131e-mcu wireless-02/09 at86rf230 table 4-6. clkm driver strength register bit value description 0 2 ma 1 4 ma 2 6 ma pad_io_clkm 3 8 ma ? bit 3 ? clkm_sha_sel refer to section 9.6.5. ? bit [2:0] ? clkm_ctrl refer to section 9.6.5. 5 application circuit an application circuit of the at86rf230 radio transceiver with a single-ended rf connector is shown in figure 5-1. the balun b1 transforms the 100 differe ntial rf port (rfp/rfn) to a 50 single-ended rf port. the capacitors c1 and c2 provide ac coupling of the rf signals to the rf pins. figure 5-1. application circuit schematic rst sel the power supply decoupling capacitors (cb2, cb4) are connected to the external analog supply pin (evdd, pin 28) and the exte rnal digital supply pin (devdd, pin 15).
9 5131e-mcu wireless-02/09 at86rf230 capacitors cb1 and cb3 are bypass capacito rs for the integrated analog and digital voltage regulators to ensure stable operation (1 f recommended value). all decoupling and bypass capacitors should be placed as close as possible to the at86rf230 pins and should have a low-resistance and low-inductance connection to ground to achieve the best performance. the crystal (xtal), the two load capacitors (cx1, cx2), and the internal circuitry connected to pins xtal1 and xtal2 form the crystal oscillator. to achieve the best accuracy and stability of the reference frequency, large parasitic capacitances should be avoided. crystal lines should be routed as short as possible and not in proximity of digital i/o signals. crosstalk from digital signals on the crystal pins or the rf pins can degrade the system performance. therefore, a low-pass filter (c 3, r2) is placed close to the clkm output pin to reduce the radiation of signal harmonics. this is not needed if the clkm pin is not used. then the output should be turned off during device initialization. the application board ground plane should be separated into four independent fragments, the analog, the digital, the antenna and the xtal ground plane. the exposed paddle shall act as reference of the individual grounds. for further details see application note avr2005 "design considerations for the at86rf230". table 5-1. example bill of materials designator description value manufacturer part number comment b1 smd balun 2.45 ghz wuerth 748421245 2.45 ghz balun b1 (alternatively) smd balun / filter 2.45 ghz johanson technology 2450fb15l0001 2.45 ghz balun / filter cb1 ldo vreg bypass capacitor 1 f cb2 power supply decoupling 1 f cb3 ldo vreg bypass capacitor 1 f cb4 power supply decoupling 1 f avx murata 0603yd105kat2a grm188r61c105ka12d x5r 10% 16v (0603) cx1 crystal load capacitor 12 pf cx2 crystal load capacitor 12 pf avx murata 06035a120ja grp1886c1h120ja01 cog 5% 50v (0603) c1 rf coupling capacitor 22 pf c2 rf coupling capacitor 22 pf epcos epcos avx b37930 b37920 06035a220jat2a c0g 5% 50v (0402 or 0603) c3 clkm low-pass filter capacitor 2.2 pf avx murata 06035a229da grp1886c1h2r0da01 cog 0.5 pf 50v (0603) designed for f clkm = 1 mhz r1 pull-down resistor 10 k recommended 0 , if continuous transmission is not required r2 clkm low-pass filter resistor 680 designed for f clkm = 1 mhz xtal crystal cx-4025 16 mhz sx-4025 16 mhz acal taitjen siward xwbbpl-f-1 a207-011
10 5131e-mcu wireless-02/09 at86rf230 6 microcontroller interface this section describes the at86rf230 to microcontroller interface. the interface comprises a slave spi and additional control signals, see figure 6-1. the spi timing and protocol are de scribed. figure 6-1. microcontroller to at86rf230 interface microcontroller at86rf230 mosi miso sclk clkm irq slp_tr mosi miso sclk gpio1/clk gpio2/irq gpio3 mosi miso sclk clkm irq slp_tr gpio4 spi sel sel sel rst rst master slave microcontrollers with a master spi, such as at mel?s avr family, interface directly to the at86rf230. the spi is used for frame buffer and register access. the additional control signals are connected to the gpio/irq interface of the microcontroller. table 6-1 introdu ces the radio transceiver i/o signals and their functionality. table 6-1. signal description of microcontroller interface signal description sel spi select signal, active low mosi spi data (master out put slave input) signal miso spi data (master inpu t slave output) signal sclk spi clock signal clkm at86rf230 clock output, usable as: - microcontroller clock source - high precision timing reference irq at86rf230 interrupt request signal slp_tr at86rf230 multi purpose control signal (functionality is state-depended): - sleep/wakeup - tx start - controls clkm output rst at86rf230 reset signal, active low
11 5131e-mcu wireless-02/09 at86rf230 6.1 spi timing description the spi is designed to work in synchronous or asynchronous mode. in synchronous mode, the clkm output of t he radio transceiver is used as the master clock of the microcontroller. in this case the maximum spi clock frequency is 8 mhz. in asynchronous mode, the spi master clock (sclk) is generated by the microcontroller itself. the maximum spi cloc k rate is limited to 7.5 mhz using this operating mode. if the clock signal from the ra dio transceiver pin clkm is not required, it may be disabled. figure 6-2 and figure 6-3 illustrate the spi timing and introduce its parameters. the corre sponding timing parameter definition is given in table 11-4. figure 6-2. spi timing, global map and definition of timing parameters t 5 , t 6 , t 8 and t 9 figure 6-3. spi timing, detailed view and definition of timing parameters t 0 to t 4 bit 7 bit 6 t 1 t 0 t 2 bit 5 t 4 t 3 bit 7 bit 6 bit 5 sclk sel mosi miso the spi is based on a byte-oriented protocol and is always a bidirectional communication between master and slave. the spi master starts the transfer by asserting sel = l. then the master generates eight spi clock cycles to transfer a byte to the radio transceiver (via mosi). at the same time the slave transmits one byte to the master (via miso). when the master wants to receive one byte of data from the slave it must also transmit one byte to the slave. all bytes are transferred msb first. an spi transaction is finished by releasing sel = h. a spi register access consists of two bytes, a frame buffer or sram access of two or more bytes, as described in section 6.2. sel = l enables the miso output driver of t he radio transceiver. the msb of miso is valid after t 1 (see section 11.4 parameter 11.4.3) and is updated at each falling edge of sclk. if the miso output driver is disabled, there is no internal pull-up resistor connected to the output. driving the appropriate signal level must be ensured by the
12 5131e-mcu wireless-02/09 at86rf230 master device or an external pull-up resistor. note, when both sel and rst are active, the miso output driver is also enabled. the mosi line is sampled by the radio transceiver at the rising edge of sclk. the signal must be stable before and after the rising edge of sclk as specified by t 3 and t 4 , refer to section 11.4 parameters 11.4.5 and 11.4.6. this mo de of spi operation is commonly called ?spi mode 0?. 6.2 spi protocol each transfer sequence starts with trans ferring a command byte from spi master via mosi (see table 6-2) with msb first. this command byte defines the access mode and addition al mode-dependent information. table 6-2. spi command byte definition bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 mode 1 0 register address [5:0] register access mode ? read access 1 1 register address [5:0] register access mode ? write access 0 0 1 reserved frame buffer access mode ? read access 0 1 1 reserved frame buffer access mode ? write access 0 0 0 reserved sram access mode ? read access 0 1 0 reserved sram access mode ? write access the different access modes are described within the following sections. in figure 6-4 to figure 6-14 logic values stated with x on mosi are ignored by the radio transceive r, but need to have a valid level. return values on miso stated as x shall be ignored by the microcontroller. 6.2.1 register access mode the register access mode is a two-byte read/ write operation and is initiated by setting sel = l. the first transferred byte on mosi is the command byte and must indicate a register access (see table 6-2) and a register address (see table 12-1). on write access the second byte transferred on mosi contains the write data to the selected address (see figure 6-4). figure 6-4. packet structure ? register write access 1 address[5:0] 1 write data[7:0] mosi xx xx miso byte 1 (command byte) byte 2 (data byte) on read access the content of the selected register address is returned in the second byte on miso (see figure 6-5).
13 5131e-mcu wireless-02/09 at86rf230 figure 6-5. packet structure ? register read access 1 address[5:0] 0 xx mosi xx read data[7:0] miso byte 1 (command byte) byte 2 (data byte) each register access must be terminated by setting sel = h. figure 6-6 illustrates a typical spi sequence for a registe r access sequence for write and read respectively. figure 6-6. example spi sequence - register access mode xx xx xx read data write command write data read command xx sclk sel mosi miso register write access register read access 6.2.2 frame buffer access modes the frame buffer read access and the frame buffer write access are used to upload or download frames to the microcontroller. each access starts by setting sel = l. the first byte transferred on mosi is the command byte and must indicate a frame buffer access mode according to the definition in table 6-2. on f rame buffer write access the second byte transferred on mosi contains the frame length (phr field) followed by the payload data (psdu) as shown by figure 6-7. figure 6-7. packet structure - frame buffer write access on frame buffer read access phr and psdu are transferred via miso starting with the second byte. after the psdu data byte s one more byte can be transferred containing the link quality indication (lqi) value of the received frame, for details refer to section 8.5. figure 6-8 illustrates the packet structure of a frame buffer read access. note, the f rame buffer read access can be terminated at any time without any consequences by setting sel = h, e.g. after reading the frame length byte only.
14 5131e-mcu wireless-02/09 at86rf230 figure 6-8. packet structure - frame buffer read access the number of bytes n for one frame buffer access is calculated as follow: receive: n = 3 + frame_length [command byte, frame length byte, psdu data, lqi byte] transmit: n = 2 + frame_length [command byte, frame length byte, psdu data] the maximum value of frame_length is 127 bytes. that means that n 130 for frame buffer read access and n 129 for frame buffer write access. each read or write of a data byte increments automatically the addr ess counter of the frame buffer until the access is terminated by setting sel = h. figure 6-9 and figure 6-10 illustrate an example spi sequence of a frame buffer acce ss to write and read a frame with 4-byte psdu respectively. figure 6-9. example spi sequence - frame buffer writ e sequence of a frame with 4-byte psdu command phr psdu 1 psdu 2 psdu 3 psdu 4 xx xx xx xx xx xx sclk sel mosi miso figure 6-10. example spi sequence - frame buffer read sequence of a frame with 4-byte psdu command xx xx xx xx xx xx phr psdu 2 psdu 1 psdu 4 psdu 3 xx lqi sclk sel mosi miso access violations during a frame buffer write or read access are indicated by a trx_ur interrupt. for further details refer to section 9.3.3. 6.2.3 sram access mode the sram access mode allows access to certain bytes within the frame buffer. this may reduce spi traffic.
15 5131e-mcu wireless-02/09 at86rf230 the sram access mode is useful, for instance , if a transmit frame is already stored in the frame buffer and certain bytes (e.g. sequence number or address field) need to be replaced before retransmitting the frame. fu rthermore, it can be used to access only the lqi value after frame reception. a detail ed description of the user accessible frame content can be found in section 9.3.2. e ach access starts by setting sel = l. the first transferred byte on mosi shall be the command byte and must indicate a sram access mode according to the definition in table 6-2. the following byte indicates the start address of the write or read access. the ad dress space is 0x00 to 0x7f. the microcontroller software has to ensure to access only to the valid address space. on sram write access, one or more bytes of write data are transferred on mosi starting with the third byte of the access sequence (see figure 6-11). figure 6-11. packet structure - sram write access on sram read access, one or more bytes of read data are transferred on miso starting with the third byte of the access sequence (see figure 6-12). figure 6-12. packet structure - sram read access as long as sel is logic low, every subsequent byte read or write increments the address counter of the frame buffer until t he sram access is terminated by setting sel = h. figure 6-13 and figure 6-14 illustrate an example spi sequence of a sram access to write an d read a data package of 5 byte length respectively. figure 6-13. example spi sequence ? sram write acce ss sequence of a 5 byte data package command address data 1 data 2 data 3 data 4 xx xx xx xx xx xx data 5 xx sclk sel mosi miso
16 5131e-mcu wireless-02/09 at86rf230 figure 6-14. example spi sequence ? sram read access sequence of a 5 byte data package command address xx xx xx xx xx xx data 2 data 1 data 4 data 3 xx data 5 sclk sel mosi miso notes: ? because the frame buffer is shared between tx and rx, the frame data are overwritten by new incoming frames. if the tx frame data is to be retransmitted, it must be ensured that no frame was received meanwhile. ? if the sram access mode is used to upload received frames, the frame buffer contains all frame data except the frame length byte. the frame length information can be accessed only using the frame buffer read access. ? it is not possible to transmit received frames without a frame buffer read and write operation by the microcontroller. ? frame buffer access violations are not i ndicated by a txr_ur interrupt when using the sram access mode (see section 9.3.3) 6.3 radio transceiver identification the at86rf230 can be identified by four registers. one register contains an unique part number and one register the corresponding version number. additional two registers contain the jedec manufacturer id. 6.3.1 register description r egister 0x1c (part_num) bit 7 6 5 4 3 2 1 0 0x1c part_num part_num read/write r r r r r r r r reset value 0 0 0 0 0 0 1 0 ? bit [7:0] ? part_num this register bits part_num contain the radio transceiver part number. table 6-3. radio transceiver part number register bits value[7:0] description part_num 2 at86rf230 part number register 0x1d (version_num) bit 7 6 5 4 3 2 1 0 0x1d version_num version_num read/write r r r r r r r r reset value 0 0 0 0 0 0 1 0
17 5131e-mcu wireless-02/09 at86rf230 ? bit [7:0] ? version_num this register bits version_num contai n the radio transceiver version number. table 6-4. radio transceiver version number register bits value[7:0] description 1 at86rf230 revision a version_num 2 at86rf230 revision b register 0x1e (man_id_0) bit 7 6 5 4 3 2 1 0 0x1e man_id_0 man_id_0 read/write r r r r r r r r reset value 0 0 0 1 1 1 1 1 ? bit [7:0] ? man_id_0 bits [7:0] of the 32 bit jedec manufacturer id are stored in register bits man_id_0. bits [15:8] are stored in register 0x1f (man _id_1). the highest 16 bits of the id are not stored in registers. table 6-5. jedec manufacturer id ? bits [7:0] register bits value[7:0] description man_id_0 0x1f atmel jedec manufacturer id bits [7:0] of 32 bit manufacturer id: 00 00 00 1f register 0x1f (man_id_1) bit 7 6 5 4 3 2 1 0 0x1f man_id_1 man_id_1 read/write r r r r r r r r reset value 0 0 0 0 0 0 0 0 ? bit [7:0] ? man_id_1 bits [15:8] of the 32 bit jedec manufacturer id are stored in register bits man_id_1. bits [7:0] are stored in register 0x1e (man _id_0). the upper 16 bits of the id are not stored in registers. table 6-6. jedec manufacturer id ? bits [15:8] register bits value[7:0] description man_id_1 0x00 atmel jedec manufacturer id bits [15:8] of 32 bit manufacturer id: 00 00 00 1f 6.4 sleep/wake-up and transmit signal (slp_tr) the slp_tr signal is a multi-functional pin. its function relates to the current state of the at86rf230 and is summarized in table 6-7. the radio transceiver states are explained in detail in section 7.
18 5131e-mcu wireless-02/09 at86rf230 table 6-7. slp_tr multi-functional pin radio transceiver status functi on transition description trx_off sleep l ? h takes the radio transceiver into sleep state sleep wakeup h ? l takes the radio transceiver into trx_off state rx_on disable clkm l ? h takes the radio transceiver into rx_on_noclk state and disables clkm rx_on_noclk enables clkm h ? l takes the radio transceiver in to rx_on state and enables clkm rx_aack_on disable clkm l ? h takes the radio transceiver into rx_aack_on_noclk state and disables clkm rx_aack_on_noclk enables clkm h ? l takes the radio transceiver into rx_aack_on state and enables clkm pll_on tx start l ? h starts frame transmission tx_aret_on tx start l ? h starts tx_aret transaction in states pll_on and tx_aret_on, the slp_tr pin is used as trigger input to initiate a tx transaction. here pin slp_tr is sensitive on rising edge only. after initiating a state change by a rising edg e at pin slp_tr in radio transceiver states trx_off, rx_on or rx_aack_on the radio transceiver remains in the new state as long as the pin is logical high and returns to the preceding state with the falling edge. the sleep state is used when radio transceiver functionality is not required, and thus the at86rf230 can be powered down to reduce the overall power consumption. a power-down scenario is shown in figure 6-15. when the radio transceiver is in trx_o ff state the microcontroller fo rce the at86rf230 to sleep by setting slp_tr = h. if the clkm output provides a clock to the microcontroller this clock is switched off after 35 clock cycles. this enables a microcontroller in a synchronous system to complete its power-down rout ine and prevent dead-lock situations. the at86rf230 awakes when the microcontroller releases pin slp_tr. this concept provides the lowest possible power consumption. figure 6-15. sleep and wake-up initiated by asynchronous microc ontroller timer output (for timing information see table 7-1) clkm slp_tr async timer (microcontroller) elapsed 35 main clock cycles ttr2 t tr2 for synchronous systems, where clkm is used as a microcontroller clock source and the spi master clock (sclk) is directly derived from clkm, the at86rf230 supports an additional power-down mode for receive operating states rx_on and rx_aack_on. if an incoming frame is expected and no other applications are running on the microcontroller, it can be powered down without missing incoming frames.
19 5131e-mcu wireless-02/09 at86rf230 this can be achieved by a rising edge on pin slp_tr which turns off the clkm output 35 clock cycles afterwards. the radio tr ansceiver state changes from rx_on or rx_aack_on to rx_on_noclk or rx_aack_on_noclk respectively. in case that a frame is received the radio transceiver enters the state busy_rx/busy_rx_aack and the clock output clkm is automatically switched on again. this scenario is shown in figure 6-16. the power consumption of the radio transceiver is similar in state rx_on_noclk/rx_aack_on_noclk and st ate rx_on, because only the clkm output is switched off. figure 6-16. wake-up initiated by radio transceiver interrupt clkm slp_tr irq transceiver irq issued 35 main clock cycles typ. 5s 6.5 interrupt logic 6.5.1 overview the at86rf230 differentiates between six interrupt events. each interrupt is enabled or disabled by writing the corresponding bi t to the interrupt mask register 0x0e (irq_mask). internally, each interrupt is stored as a separate bit of the interrupt status register. all interrupt lines are combined via logical ?or? to one external interrupt line (irq). if the irq pin issues, the microcontrolle r shall read the interrupt status register 0x0f (irq_status) to determine the reason for the interrupt. a read access to this register clears the interrupt status regist er and the irq pin, too. interrupts are not cleared automatically when the event that ca used them is not valid anymore. exception: the pll_lock irq clears the pll_unlock irq and vice versa. the supported interrupts for the basic operating mode (see section 7.1) are summarized in table 6-8. table 6-8. interrupt description in basic operating mode irq name comments details irq_7: bat_low indicates a supply voltage below the programmed threshold. section 9.5.3 irq_6: trx_ur indicates a frame buffer access violation (under run). section 9.3.3 irq_3: trx_end rx: indicates the completion of a frame reception. tx: indicates the completion of a frame transmission. section 7.1.3 sect ion 7.1.3 irq_2: rx_start indicates a sfd detection. the trx_state changes to busy_rx. section 7.1.3 irq_1: pll_unlock indicates pll unlock. the pa is turned off immediately, if the radio transceiver is in busy_tx/busy_tx_aret state. section 9.7.4 irq_0: pll_lock indicates pll lock section 9.7.4 using the extended operating mode, the interrupts are handled in a slightly different way. a detailed description can be found in section 7.2.4.
20 5131e-mcu wireless-02/09 at86rf230 6.5.2 register description regis ter 0x0e (irq_mask) the irq_mask register is used to enable (set re gister bit to 1) or disable (set register bit to 0) interrupt events by writing the co rresponding bit to the interrupt mask register. bit 7 6 5 4 0x0e mask_bat_low mask_trx_ur reserved irq_mask read/write r/w r/w r/w r/w reset value 1 1 1 1 bit 3 2 1 0 0x0e mask_trx_end mask_rx_start mask_pll_unlock mask_pll_lock irq_mask read/write r/w r/w r/w r/w reset value 1 1 1 1 if an interrupt will be enabled or disabled, it is recommended to read the interrupt status register 0x0f (irq_status) first to clear the history. register 0x0f (irq_status) the irq_status register contains the stat us of the individual interrupts. a read access to this register resets all interrupt bits. bit 7 6 5 4 0x0f bat_low trx_ur reserved irq_status read/write r r r r reset value 0 0 0 0 bit 3 2 1 0 0x0f trx_end rx_start pll_unlock pll_lock irq_status read/write r r r r reset value 0 0 0 0 by reading the register after an interrupt is signaled at irq pin, the reason for the interrupt can be identified. a detailed description of the individual interrupts can be found in table 6-8.
21 5131e-mcu wireless-02/09 at86rf230 7 operating modes 7.1 basic operating mode this section summarizes all states to provide the basic functionality of the at86rf230, such as receiving and transmitting frames, and powering up and down. the basic operating mode is designed for ieee 802.15.4 applications ; the corresponding radio transceiver states are shown in figure 7-1. figure 7-1. basic operating mode state diagram (for state transition timing data refer to table 7-1) t r x _ o f f s l p _ t r = h s l p _ t r = l p l l _ o n r x _ o n t r x _ o f f t r x _ o f f s l p _ t r = h s l p _ t r = l sfd detected 7.1.1 state control the radio transceiver state is controlled by two signal pins (slp_tr, rst ) and the register 0x02 (trx_state). a successful state change shall be confirmed by reading the radio transceiver status fr om register 0x01 (trx_status). if trx_status = 0x1f (state_transition_in_progress) the at86rf230 is on a state transition. do not try to initiate a further state change while the radio transceiver is in state_ transition_in_progress.
22 5131e-mcu wireless-02/09 at86rf230 the pin slp_tr is a multifunctional pin. depending on radio transceiver state the rising edge of slp_tr causes the following state transitions: ? trx_off ? sleep ? rx_on ? rx_on_noclk ? pll_on ? busy_tx for further details to the functionality of pin slp_tr refer to section 6.4. the pi n rst causes a reset of all registers (register bits clkm_sha_sel and clkm_ctrl are shadowed, for details refer to section 9.6.4) and forces the radio transceive r into trx_off state. however, if the device is in the p_on state it remains in the p_on state. for all states, the state change commands force_trx_off or trx_off lead to a transition into trx_off state. if the radio transceiver is in the busy_rx or busy_tx state, the command force_trx_off interrupts the active receiving or transmitting process, and forces an immediate transition. in contrast to that the trx_off command is stored until a currently ongoing frame reception or transmission has finished. after the end of the frame, the transition to trx_off is performed. the completion of each requested state change shall always be confirmed by reading the register 0x01 (trx_status). 7.1.2 basic operating mode description 7.1.2.1 p_on - po wer-on after v dd when the external supply voltage (v dd ) is firstly applied to the radio transceiver, the system goes into the p_on state. an on-chi p reset is performed. the crystal oscillator gets activated and the master clock is provided to the clkm pin after the crystal oscillator has stabilized. clkm can be used as a clock source to the microcontroller. the on-chip power-on-reset sets all registers to their default values. a dedicated reset signal from the microcontroller at the pin rst is not necessary, but recommended for hardware/software synchronization reasons. the reset impulse should have a minimum length as specified in section 11.4, see parameter 11.4.12. all digital inputs have pull -up or pull-down resistors (see table 4-4). this is necessary to su pport microcontrollers where gpio signals are floating after reset. the input pull- up and pull-down resistors are disabled when the radio transceiver leaves the p_on state. prior to leaving p_on, the microcontroller must set all digital input pins (mosi, rst , sclk, sel , slp_tr) to their default operating values. once the supply voltage has stabilized and the crystal oscillator has settled (see section 11.5, parameter 11.5.5), a spi write access to the register 0x02 (trx_state) with the comm and trx_off or force_trx_off initiates a state change from p_on to trx_off. 7.1.2.2 sleep ? sleep state in sleep state, the entire radio transceiver is disabled. no circuitry is operating. the at86rf230 current consumption is reduced to leakage current only. this state can only be entered from state trx_off by setting the pin slp_tr = h. if clkm is enabled, the sleep state is entered 35 clkm cycles after the rising edge. at that time clkm is turned off. if the clkm out put is turned off (bits clkm_ctrl = 0 in register 0x03), the sleep state is entered immediately.
23 5131e-mcu wireless-02/09 at86rf230 setting slp_tr = l returns the radio transceiver to the trx_off state. it is recommended that pin slp_tr should be active for a minimum of 40 clkm cycles to completely power down the radio transceiver. during sleep state, the register contents remain valid while the content of the frame buffer is cleared. 7.1.2.3 trx_off ? clock state in trx_off state the spi interface and the crystal oscillator are enabled. the digital voltage regulator (dvreg) is enabled and provid es 1.8v to the digital core to make the frame buffer available (see section 9.1). the microcontroller can access all digital function s and if enabled, the clkm output supplies a clock. the pin slp_tr is enabled for state control. 7.1.2.4 pll_on ? pll state entering the pll_on state from trx_off st ate enables the analog voltage regulator (avreg) first. after the voltage regulator has been settled, the pll frequency synthesizer is enabled. when the pll ha s been settled at the receive frequency, a successful pll lock is indicat ed by issuing a pll_lock interrupt. if an rx_on command is issued in pll_on state, the receiver is immediately enabled. if the pll has not been settled before, actual frame reception can only happen once the pll has locked. the pll_on state corr esponds to the tx_on state in ieee 802.15.4. 7.1.2.5 rx_on and busy_rx ? rx listen and receive state in rx_on state the receiver blocks and the pll frequency synthesizer are enabled. the at86rf230 receive mode is internally divided into rx_on state and busy_rx state. there is no difference between thes e states with respect to the analog radio transceiver circuitry, which is always turn ed on. during rx_on state, only the preamble detection of the digital signal processing is running. when a preamble and a valid sfd are detected, also the digital receiver is turned on. the radio transceiver enters the busy_rx state and a rx_start interrupt is generated. during the frame reception frame data are stored continuously in the frame buffer until the last byte was received. the completion of the frame reception is indicated by a trx_end interrupt and the radio transceive r reenters the state rx_on. at the same time the register bit rx_crc_valid (register 0x06) is updated with the result of the fcs check (see section 8.2). note, setting s of address registers 0x20 to 0x2b do not affect the frame reception in basic operating mode. frame address filter ing is only applied when using the extended operating mode (see section 7.2). 7.1.2.6 rx_on_noclk ? rx listen state without clkm if the radio transceiver is listening for an incoming frame and the microcontroller is not running an application, the microcontroller can be powered down to decrease the total system power consumption. this special po wer-down scenario for systems running in clock synchronous mode (see section 6.4) is supported by the at86rf230 using the state rx_ on_noclk. this state can only be entered by setting slp_tr = h while the at86rf230 is in the rx_on state. the clkm pin is disabled 35 clock cycles after the rising edge at the slp_tr pin. this allows the microcontrolle r to complete its power-down sequence. the
24 5131e-mcu wireless-02/09 at86rf230 reception of a frame is indicated to the mi crocontroller by a rx_start interrupt. clkm is turned on again, and the radio transceiver enters the busy_rx state (see section 6.4, figure 6-16). the end of the transaction is indicated to the microcontroller by a trx_end interrupt. after the transaction has been completed, the radio transceiver enters the rx_on state. the radio transceiver only reenter s the rx_on_noclk state, when the next rising edge at pin slp_tr occurs. if the radio transceiver is in the rx_on_noclk state, and the slp_tr pin is reset to logic low, it enters the rx_on state, and it starts to supply clock on the clkm pin again. in states rx_on_noclk and rx_on, the current consumption is about the same, because only the clkm output is switched off in state rx_on_noclk. 7.1.2.7 busy_tx ? transmit state a transmission can only be started in state pll_on. there are two ways to start a transmission: ? rising edge of slp_tr ? tx_start command to register 0x02 (trx_state). either of these causes the at86rf230 to enter the busy_tx state. during the transition to busy_tx state, the pll frequency shifts to the transmit frequency. transmission of the first data chip of the preamble starts after 16 s to allow pll settling and pa ramping, see figure 7-2. after transmission of the preamble and the sfd, the frame buffe r content is transmitted. the last two bytes to be transmitted are the fcs (see figure 8-2). the radio transceiver can be configured to autonomously compute the fcs bytes and append it to the transmit data. the register bit tx_auto_crc_on in register 0x05 (phy_tx_pwr) needs to be set to 1 to enable this feature. for further details refer to section 8.2.when the frame tra nsmission is completed, the r adio transceiver automatically turns off the power amplifier, generates a trx_end in terrupt and returns to pll_on state. note that in case the phr indicates a fram e length of zero, the transmission is aborted. 7.1.3 interrupt handling in basic operating mode all interrupts of the at86rf230 (see table 6-8) are supported during operation in basic operating mo de. two interrupts are used to support rx and tx operation of the radio transceiver. on receive the rx_start interrupt indicates the detection of a valid sfd. the trx_end interrupt indicates the completion of the frame reception or frame transmission. figure 7-2 shows a receive/transmit transacti o n and the related interrupt events in basic operating mode. one device is assumed to operate as transmitter (device 1), the second one as receiver (device 2). processing delays are typical values.
25 5131e-mcu wireless-02/09 at86rf230 figure 7-2. timing of rx_start and trx_end interrupts in basic operating mode (see register 0x0f) 128 160 192 0 352 -16 time [s] rx (device 2) frame on air trx_end tx (device1) pll_on busy_tx pll_on irq slp_tr trx_state typ. processing delay 16 s trx_end rx_start 8 s 16 s rx_listen busy_rx rx_listen irq trx_state typ. processing delay preamble sfd phr psdu 41 1 5 number of octets frame content 7.1.4 basic mode timing the following paragraphs depict the transit ions between states and their timing. 7.1.4.1 power-on and wake-up procedure the power-on sequence and the wake-up procedure is shown in figure 7-3. figure 7-3. wake-up procedure from sleep and p_on to rx_on (pll locked) 06 0 0 500 700 active blocks 800 900 1000 1100 ftn bg dvreg avreg 16 s pll timer 256 s timer 128 s trx_off state pll_on command pll_on, rx_on slp_tr=0 xosc typical block settling time, stays on block active waiting for spi commands xosc delivers clock clkm delivers clock clock stable irq pll locked signals/events rx_on rx_on sleep pin ~400 time [ s] time [ s] timer 128 s evdd on xosc trx_off p_on clkm_ctrl active blocks state command signals/events setting pin slp_tr = l in sleep state enables the crystal oscillator. after 0.4 ms (typ.), the internal clock signal is available. after another 128 s the clock signal is provided at the clkm pin if enabled. an additi onal 256 s timer ensures that frequency stability is sufficient to drive filter tuning (ftn) and the pll. after the digital voltage regulator has been settled, the radio transceiver enters the trx_off state and waits for further commands.
26 5131e-mcu wireless-02/09 at86rf230 in trx_off state, entering the commands pll_on or rx_on initiates a ramp-up sequence of the analog voltage regulator. rx_on state can be entered any time during pll_on state regardless whether the pll has already locked. when the wake-up sequence is started from p_on state (v dd first applied to the radio transceiver) the state machine stops after the 128 s timer expires to wait for a valid trx_off command from the microcontroller. the default clkm frequency in p_on state is 1 mhz. 7.1.4.2 reset procedure rst = l sets all registers to their default values (see table 12-2). exception, register bits clkm _ctrl of register 0x03 (trx_ctr l_0) are shadowed at reset. for details refer to section 9.6.4. after relea sing the reset pin ( rst = h) a calibration cycle of the ftn is started and the digital voltage regulator is turned on. the state trx_off is entered and the status of the main state machine changes from state_tran sition_in_progress to trx_off. this sequence is identical for all radio transceiver states except in state p_on. the state machine does not leave the state p_on a fter a reset in this state. instead, the procedure described in section 7.1.2.1 must be followed to enter the trx_off state for the very first time. figure 7-4 describes the reset procedure once the p_on state was left. note th at the access to the device should not occur earlier than 625 ns after releasing the reset pin. during the reset procedure the spi interface shall be inactive ( sel = h; sclk = l). figure 7-4. reset procedure x+100 active blocks ftn bg dvreg trx_off state command xosc typical block settling time, stays on block active waiting for spi commands signals/events reset rst=1 pin x time [ s] time [ s] rst=0 020 7.1.4.3 state transition timing the transition numbers (first column) in table 7-1 correspond to figure 7-1 and do not inclu de spi access time if not otherwise stated. see measurement setup in figure 5-1. table 7-1. state transition timing no symbol transition time [s] (tppical) comments 1 t tr1 p_on : trx_off 880 depends on external bypass capacitor at dvdd (1 f nom) and crystal oscillator setup (cl = 10 pf) 2 t tr2 sleep : trx_off 880 depends on external bypass capacitor at dvdd (1 f nom) and crystal oscillator setup (cl = 10 pf) 3 t tr3 trx_off : sleep 35 f clkm = 1 mhz 4 t tr4 trx_off : pll_on 180 depends on external bypass capacitor at avdd (1 f nom).
27 5131e-mcu wireless-02/09 at86rf230 no symbol transition time [s] (tppical) comments 5 t tr5 pll_on trx_off 1 6 t tr6 trx_off rx_on 180 depends on external bypass capacitor at avdd (1 f nom). 7 t tr7 rx_on trx_off 1 8 t tr8 pll_on rx_on 1 9 t tr9 rx_on pll_on 1 10 t tr10 pll_on busy_tx 16 when asserting slp_tr pin first symbol transmission is delayed by 16 s (pll settling and pa ramp up). 11 t tr11 busy_tx pll_on 32 32 s pll settling time 12 t tr12 all states trx_off 1 using trx_cmd force_trx_off (see register 0x02), not valid for sleep mode 13 t tr13 rst = l trx_off 120 depends on external bypass capacitor at dvdd (1 f nom), not valid for p_on mode the state transition timing is calculated based on the timing of the individual blocks as shown in figure 7-3. the worst case values include maximum operating temperature, minimum sup ply voltage, and device parameter variations. table 7-2. block settling time block time [s] (typical) time [s] (worst case) comments xosc 500 1000 until clock signal is provided at clkm pin. depends on crystal q factor and load capacitor dvreg 60 1000 depends on external bypass capacitor at dvdd (cb3 = 1 f nom., 10 f worst case) avreg 60 1000 depends on external bypass capacitor at avdd (cb1 = 1 f nom., 10 f worst case) pll, initial 100 150 pll, rx tx 16 pll settling time pll, tx rx 32 pll settling time 7.1.5 register description regis ter 0x01 (trx_status) the trx_status register signals the current state of the radio transceiver as well as the status of the cca measurement. note, a r ead access to the register clears bits cca_done and cca_status. this register is used for extended and ba sic operating mode. the extended operating mode functionality is described in section 7.2. bit 7 6 5 4 0x01 cca_done cca_status reserved trx_status trx_status read/write r r r r reset value 0 0 0 0
28 5131e-mcu wireless-02/09 at86rf230 bit 3 2 1 0 0x01 trx_status trx_status read/write r r r r reset value 0 0 0 0 ? bit 7 ? cca_done refer to section 8.6. ? bit 6 ? cca_status refer to section 8.6. ? bit 5 ? reserved ? bit [4:0] ? trx_status the register bits trx_status signal the current radio transceiver status. if the requested state transition is not co mpleted yet, the trx_status returns state_transition_in_progress. state transition timings are defined in table 7-1. table 7-3. radio transceiver status, register bits trx_status register bits value[4:0] state description 0x00 p_on 0x01 busy_rx 0x02 busy_tx 0x06 rx_on 0x08 trx_off (clock state) 0x09 pll_on (tx_on) 0x0f sleep 0x11 (1) busy_rx_aack 0x12 (1) busy_tx_aret 0x16 (1) rx_aack_on 0x19 (1) tx_aret_on 0x1c rx_on_noclk 0x1d (1) rx_aack_on_noclk 0x1e (1) busy_rx_aack_noclk 0x1f state_transition_in_progress trx_status all other values are reserved notes: 1. extended operating mode only, refer to section 7.2. register 0x02 (trx_state) the register trx_state controls the radio transceiver states via register bits trx_cmd. the status and the result of a tx_aret/rx_aack transaction is indicated by register bits trac_status. a successful state transition shall be conf irmed by reading register bits trx_status in register 0x01 (trx_status). this register is used for basic and exte nded operating mode. the extended operating mode functionality is described in section 7.2.
29 5131e-mcu wireless-02/09 at86rf230 bit 7 6 5 4 0x02 trac_status trx_cmd trx_state read/write r r r r/w reset value 0 0 0 0 bit 3 2 1 0 0x02 trx_cmd trx_state read/write r/w r/w r/w r/w reset value 0 0 0 0 ? bit [7:5] ? trac_status refer to section 7.2.6. ? bit [4:0] ? trx_cmd a write access to register bits trx_cmd in itiates a radio transceiver state transition towards the new state. table 7-4. state control commands, register bits trx_cmd register bits value[4:0] state transition towards 0x00 (1) nop 0x02 (2) tx_start 0x03 force_trx_off 0x06 rx_on 0x08 trx_off (clock state) 0x09 pll_on (tx_on) 0x16 (3) rx_aack_on 0x19 (3) tx_aret_on trx_cmd all other values are reserved notes: 1. trx_cmd = 0 after power-on reset (por) only 2. frame transmission starts 16 s (1 symbol) after tx_start 3. extended operating mode only, refer to section 7.2 7.2 extended operating mode the extended operating mode goes beyond th e basic radio transceiver functionality provided by the basic operating mode. specific functionality requested by the ieee 802.15.4-2003 standard is supported such as automatic acknowledgement and automatic frame retransmissi on. this results in a more efficient ieee 802.15.4-2003 software mac implementation including reduced code size, the possible use of a smaller microcontroller or the ability to simplify the handling of time-critical tasks. the extended operating mode is designed to support ieee 802. 15.4-2003 standard compliant frames. while using the extended operating mode, the at86rf230 radio transceiver supports: ? automatic address filtering ? automatic acknowledgement (rx_aack) and ? automatic csma-ca with optional frame retransmission (tx_aret) note, the extended operating mode does not support slotted csma-ca.
30 5131e-mcu wireless-02/09 at86rf230 the rx_aack transaction consists of: ? frame reception ? address filtering and automatic fcs check ? interrupt indicating frame reception, if it passes address filtering and fcs check ? automatic ack frame transmission, if necessary for details on rx_aack transaction see section 7.2.3.1. the tx_are t transaction consists of: ? csma-ca including automatic retry ? frame transmission and automatic fcs field generation ? reception of ack frame, if requested ? automatic retry of transmissions if ack was expected but not received ? interrupt and transaction return code generation for details on tx_aret transaction see section 7.2.3.2. the at86 rf230 state diagram including the extended operating mode states is shown in figure 7-5. yellow marked states represent the basic operating mode, blue marked states represent the extended operating mode.
31 5131e-mcu wireless-02/09 at86rf230 figure 7-5. extended operating mode state diagram 2 t r x _ o f f s l p _ t r = h s l p _ t r = l p l l _o n rx_on pll_on trx_off (clock state) xosc=on pull=off r x _ o n p_on (power-on after vdd) xosc=on pull=on sleep (sleep state) xosc=off pull=off (all states except p_on) force_trx_off (all states except sleep) frame end frame end busy_tx (transmit state) pll_on (pll state) rx_on (rx listen state) busy_rx (receive state) t r x _ o f f t r x _ o f f 1 3 4 5 7 6 8 9 11 10 rx_on_noclk (rx listen state) clkm=off s l p _ t r = h s l p_tr =l tx_aret_on rx_aack_on busy_rx_aack busy_tx_aret trans- action finished frame end p l l _ o n r x _ a a c k _ o n rx_aack_ on_noclk busy_rx_ aack_noclk frame rejected t x _ a r e t _ o n r x _ a a c k _ o n from trx_off from trx_off 12 13 tx_start slp_tr=h or tx_start slp_tr=h or clkm=off clkm=off sfd detected sfd detected sfd detected reset rst=h (from all states) rst=l legend: blue: spi write to register trx_state (0x02) red: control signals via ic pin green: event basic operating mode states extended operating mode states state transition number, timing data in table 7-1 x 7.2.1 state control the extended operating mode states can be entered from states trx_off or pll_on as described by the state diagram in figure 7-5. the completion of each requ ested state change shall always be c onfirmed by reading the register 0x01 (trx_status).
32 5131e-mcu wireless-02/09 at86rf230 rx_aack: the state rx_aack_on is entered by writing the command rx_aack_on to the register bits trx_cmd in register 0x02 (trx_state). the state change shall be confirmed by reading register 0x01 (trx_status) that changes to rx_aack_on or busy_rx_aack on success. tx_aret: similarly, tx_aret_on state is activated by setting register bits trx_cmd (register 0x02) to tx_aret_on. the radio transceiv er is in the tx_aret_on state after trx_status (register 0x01) has changed to tx_aret_on. notes: 1. it is not recommended to use the force_trx_off command while being in state busy_tx_aret without appending a sleep cy cle by activating slp_tr for at least 2 s. 2. after state transition from state rx_a ack_on to state pll_ on, start of frame transmission shall be confirmed by readi ng register 0x01 (trx_status). if register bits trx_status do not return busy_tx during frame transmission, the frame transmission needs to be initiated again. if the frame has been downloaded before initiating the frame transmission, it has to be downloaded again. 7.2.2 configuration the use of the extended operating m ode is based on basic operating mode functionality. only features beyond the basic radio transceiver functionality are described in the following sections. for details to the basic operating mode refer to section 7.1. whe n using the rx_aack or tx_aret modes, the following registers needs to be configured. rx_aack: ? setup registers 0x20 ? 0x2b for pan-id and ieee addresses ? set register bit aack_set_pd (register 0x2e) ? configure register bit i_am_coord (register 0x2e) tx_aret: ? configure csma-ca - max_frame_retries (register 0x2c) - max_csma_retries (register 0x2c) - csma_seed (registers 0x2d, 0x2e) - min_be (register 0x2e) ? configure cca (see section 8.7) the min_be register bits (register 0x2e) sets the minimum back-off exponent (refer to ieee 802.15.4-2003 section 7.5.1.3), and the csma_seed_0 and csma_seed_1 register bits (registers 0x2d , 0x2e) define a random seed for the back-off-time random- number generator in the at86rf230. the re gister bits max_csma_retries (register 0x2c) configures how often the radio transce iver retries the csma-ca algorithm after a busy channel is detected. max_frame_retries (register 0x2c) defines the maximum number of frame retransmissions.
33 5131e-mcu wireless-02/09 at86rf230 7.2.3 extended operating mode description 7.2.3.1 rx_aack_ on ? receive with automatic ack in the rx_aack_on state, the radio transceiver listens for incoming frames. after detecting a frame start (sfd), the radio transceiver state changes to busy_rx_aack (register 0x01) and the trac_status bits (register 0x02) are set to invalid. the at86rf230 starts to parse the mac header (mhr) and a filtering procedure as described in ieee 802.15.4- 2003 section 7.5.6.2. (third level filter rules) is applied accordingly. it accepts only frames that sa tisfy all of the following requirements (quote from ieee 802.15.4 2003): ? the frame type subfield of the frame contro l field shall not contain an illegal frame type. ? if the frame type indicates that the frame is a beacon frame, the source pan identifier shall match macpanid unless macpanid is equal to 0xffff, in which case the beacon frame shall be accepted rega rdless of the source pan identifier. ? if a destination pan identifier is included in the frame, it shall match macpanid or shall be the broadcast pan identifier (0xffff). ? if a short destination address is included in the frame, it shall match either macshortaddress or the broadcast addr ess (0xffff). otherwise, if an extended destination address is included in the frame, it shall match an extendedaddress. ? if only source addressing fields are incl uded in a data or mac command frame, the frame shall be accepted only if the devic e is a pan coordinator and the source pan identifier matches macpanid. any frames rejected by these rules are discarded. the at86rf230 requires to satisfy two additional rules: ? the frame type indicates that the fr ame is not an ack frame (refer to table 8-1) ? at least one address field must be present (refer to table 8-2) a frame is al so discarded if the fcs is invalid. otherwise, the trx_end interrupt is issued and the register bits trac_status are set to success after the reception of the frame was completed. the microcontroller can then upload the frame. the at86rf230 detects whether an ack frame needs to be sent. in that case, the radio transceiver automatically generates an ack frame which is transmitted 12 symbol periods after the end of the received frame. if the frame that needs to be acknowledged is a valid mac command data request frame, the content of register bit aack_set_pd in register 0x2e (csma_seed_1) is copied to the frame pending subfield of the ack and the frame sequence number is copied likewise. during these operations the radio transceiver remains in busy_rx_aack state. after the completion of the rx_aack transac tion the radio transceiver reenters the state rx_aack_on. the flow diagram of the rx_aack algorithm is shown in figure 7-6. the timing of an rx_aack transaction is shown in figure 7-7. it shows a reception of a data frame of length 10 with the ack request bit set to one. a state change to busy_rx_aack is performed after sfd detection. the completion of the frame reception is indicated by a trx_end interrupt. the ack frame is transmitted after a wait period of 12 symbols (192 s).
34 5131e-mcu wireless-02/09 at86rf230 figure 7-6. flow diagram of rx_aack figure 7-7. example timing of an rx_aack transaction rx/tx frame on air rx_aack_on busy_rx_aack trx_state frame type rx_aack_on rx/tx rx tx trx_end irq rx typ. processing delay 16 s 192 s (12 symbols) 512 0 704 time [ s] 64 1088 data frame (length = 10, ack=1) ack frame sfd
35 5131e-mcu wireless-02/09 at86rf230 7.2.3.2 tx_aret_on ? transmit with automatic csma-ca retry the implemented tx_aret algorithm is shown in figure 7-8. the tx_a ret transaction is started by either a rising edge on slp_tr pin or by writing a tx_start command to register 0x02 (trx _state). the radio transceiver sets the trac_status bits to invalid and execut es the csma-ca algorithm as defined by ieee 802.15.4-2003 section 7.5. 1.4. if a clear channel is detected during csma-ca execution, the radio transceiver proceeds to transmit the frame. during frame transmission the at86rf230 parses the frame control field of the downloaded frame to check if an ack reply is expected. if an ack is expected, the radio transceiver switches into receive mode to wait for valid ack reply. an ack is considered as valid if its fcs is correct, and if the sequence number of the ack matches the sequence number of the previously transmitted frame. if no valid ack is received or a timeout (after 864 s) occurred, the radio transceiver retries the entire transaction, including csma-ca execution. this repeats until the frame has been acknowledged or the maximum number of retransmissions (as set by the register bits max_frame_retries in register 0x2c) has been reached. in this case, the trx_end interrupt is issued and the value of trac_status is set to no_ack. if a valid ack is found, the trx_end interrupt is issued. the frame pending subfield of the ack frame is parsed and the regist er bits trac_status are updated. if the frame pending subfield of the ack fram e is set, trac_status is updated with success_data_pending, otherwise trac _status is updated with success. while in receive mode for ack reception, incoming data do not overwrite the frame buffer content. transmit data in the frame buffer are not changed during the tx_aret transaction. if no ack is expected, the radio transceiver issues a trx_end interrupt after the frame transmission has been completed. the value of register bits trac_status (register 0x02) is set to success. if the csma-ca did not detect a clear channel, the channel access is retried as often as specified by the register bits max_csma _retries (register 0x2c). in case that csma-ca does not detect a clear ch annel after max_csma_retries, the transaction is aborted and the trx_end interrupt is issued. the trac_status register bits are updated with channel_access_failure. note that it is recommended to download the transmit data before starting a tx_aret transaction.
36 5131e-mcu wireless-02/09 at86rf230 figure 7-8 flow diagram of tx_aret figure 7-9 shows a tx_aret transaction with the related timing. in this example a data frame of length 10 with ack request is transmitted. furthermore the following constrains are assumed: ? register bits min_be (register 0x2e) are se t to 0 to not delay the execution of the cca algorithm after the rising edge at pin slp_tr ? a clear channel is assumed (no csma-ca retry, no frame retransmission).
37 5131e-mcu wireless-02/09 at86rf230 figure 7-9 timing example of a tx_aret transaction rx/tx frame on air tx_aret_on busy_tx_aret trx_state frametype tx_aret_on rx/tx c s m a - c a rx trx_end irq typ. processing delay 16 s 672 0 x time [ s] 128 x+352 slp_tr tx 128 s 32 s 16 s data frame (length = 10, ack=1) ack frame register settings: 0x2c: max_frame_retries=0 0x2c: max_csma_rrtries=0 0x2e: min_be=0 7.2.3.3 rx_aack_on_noclk ? rx_aack_on without clkm if the at86rf230 is listening for an incoming frame and the microcontroller is not running an application, the microcontroller can be powered down to decrease the total system power consumption. this special po wer-down scenario for systems running in clock synchronous mode (see section 6.4) is supported by the at86rf230 using the state rx _aack_on_noclk. the radio transceiver functionality in this state is based on that in state rx_aack_on (see section 7.2.3.1), only the clock on pin clkm is disa bled. the rx_aack_on_noclk state is entered from rx_aack_on by a rising edge at slp_tr pin. the return to rx_aack_on stat e results either from a successful frame reception or a falling edge on pin slp_tr. the clkm pin is disabled 35 clock cycles after the rising edge at slp_tr pin. this allows the microcontroller to co mplete its power-down sequence. in case of frame reception, the radio tr ansceiver enters the busy_rx_aack_on state and parses the address field and the fcs of the incoming frame. if it passes address filtering and has a correct fcs the frame is accepted and the radio transceiver state changes to busy_rx_aack, the trx_end interrupt is issued and clkm is turned on. if an ack was requested the radio transcei ver follows the procedure described in section 7.2.3.1. after the transactio n has been completed, the radio transceiver enters the rx_aack_on state. note, the radio trans ceiver reenters the rx_aack_on_noclk state only, when the next rising edge at slp_tr pin occurs. 7.2.4 interrupt handling in extended operating mode the interrupts in the extended operating m ode are handled slightly different compared to the basic operating mode (see section 7.1.3). the number of possible interrupts is redu ced to a necessary minimum of events. this minimizes the interaction between microcontroller and at86rf230 to reduce the overall power consumption. the differences in the interrupt handling are described in table 7-5.
38 5131e-mcu wireless-02/09 at86rf230 table 7-5. interrupt description for extended operating mode irq handling in exte nded operating mode irq_7: bat_low no special handling (see section 6.5) irq_6: trx_ur no special handling (see section 6.5) irq_3: trx_end tx_aret: indicates the completion of tx_aret algorithm. rx_aack: indicates the successful frame reception. frame data can be uploaded to the microcontroller. irq_2: rx_start not used irq_1: pll_unlock disabled for regular operation. in case of occurrence, the device status needs to be examined (refer to avr2009 ?at86rf230 ? software programming model?). irq_0: pll_lock disabled for regular operation. in case of occurrence, the device status needs to be examined (refer to avr2009 ?at86rf230 ? software programming model?). 7.2.5 register summary table 7-6. register summary reg.-address register name description 0x01 trx_status radio transceiver status, cca result 0x02 trx_state state control 0x20 - 0x2b address filter configuration 0x2c xah_ctrl retries value control 0x2d csma_seed_0 csma-ca seed value 0x2e csma_seed_1 csma-ca seed valu e, min_be, aack_set _pd, i_am_coord 7.2.6 register description ? control registers regis ter 0x01 (trx_status) the trx_status register signals the current state of the radio transceiver as well as the status of the cca measurement. note, a r ead access to the register clears bits cca_done and cca_status. this register is also used for basic operating mode, refer to section 7.1. bit 7 6 5 4 0x01 cca_done cca_status reserved trx_status trx_status read/write r r r r reset value 0 0 0 0 bit 3 2 1 0 0x01 trx_status trx_status read/write r r r r reset value 0 0 0 0 ? bit 7 ? cca_done refer to section 8.6.
39 5131e-mcu wireless-02/09 at86rf230 ? bit 6 ? cca_status refer to section 8.6. ? bit 5 ? reserved ? bit [4:0] ? trx_status the register bits trx_status signal the current radio transceiver status. if the requested state transition is not co mpleted yet, the trx_status returns state_transition_in_progress. state transition timings are defined in table 7-1. table 7-7. radio transceiver status, register bits trx_status register bits value[4:0] state description 0x00 p_on 0x01 busy_rx 0x02 busy_tx 0x06 rx_on 0x08 trx_off (clock state) 0x09 pll_on (tx_on) 0x0f sleep 0x11 busy_rx_aack 0x12 busy_tx_aret 0x16 rx_aack_on 0x19 tx_aret_on 0x1c rx_on_noclk 0x1d rx_aack_on_noclk 0x1e busy_rx_aack_noclk 0x1f state_transition_in_progress trx_status all other values are reserved register 0x02 (trx_state) the register trx_state controls the radio transceiver states via register bits trx_cmd. the status and the result of a tx_aret/rx_aack transaction is indicated by register bits trac_status. a successful state transition shall be conf irmed by reading register bits trx_status in register 0x01 (trx_status). bit 7 6 5 4 0x02 trac_status trx_cmd trx_state read/write r r r r/w reset value 0 0 0 0 bit 3 2 1 0 0x02 trx_cmd trx_state read/write r/w r/w r/w r/w reset value 0 0 0 0
40 5131e-mcu wireless-02/09 at86rf230 ? bit [7:5] ? trac_status the status of the tx_aret algorithm is i ndicated by register bits trac_status. details of the algorithm and a description of the status information are given in section 7.2.3.2. table 7-8. state control register, register bits trac_status tx_aret register bits value[7:5] description 0 success 1 success_data_pending 3 channel_access_failure 5 no_ack 7 invalid trac_status all other values are reserved ? bit [4:0] ? trx_cmd a write access to register bits trx_cmd in itiates a radio transceiver state transition towards the new state. table 7-9. state control register, register bits trx_cmd register bits value[4:0] state description 0x00 (1) nop 0x02 (2) tx_start 0x03 force_trx_off 0x06 rx_on 0x08 trx_off (clock state) 0x09 pll_on (tx_on) 0x16 rx_aack_on 0x19 tx_aret_on trx_cmd all other values are reserved notes: 1. trx_cmd = 0 after power-on reset (por) 2. frame transmission starts 16 s (1 symbol) after tx_start register 0x2c (xah_ctrl) the xah_ctrl register controls the tx_a ret transaction in the extended operating mode of the radio transceiver. bit 7 6 5 4 0x2c max_frame_retries xah_ctrl read/write r/w r/w r/w r/w reset value 0 0 1 1 bit 3 2 1 0 0x2c max_csma_retries reserved xah_ctrl read/write r/w r/w r/w r/w reset value 1 0 0 0
41 5131e-mcu wireless-02/09 at86rf230 ? bit [7:4] ? max_frame_retries max_frame_retries specifies the maximum number of frame retransmission in tx_aret transaction. ? bit [3:1] ? max_csma_retries max_csma_retries specifies the maximum number of retries in tx_aret transaction to repeat t he random back-off/cca procedur e before the transaction gets cancelled. even though the valid range of max_csma_retries is [0, 1 ? 5] according to ieee 802.15.4-2003, the at86rf230 can be configured up to a maximum value of 7 retries. ? bit 0 ? reserved register 0x2d (csma_seed_0) the csma_seed_0 register c ontains a fraction of the csma_seed value for the csma-ca algorithm. bit 7 6 5 4 3 2 1 0 0x2d csma_seed_0 csma_seed_0 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 1 1 1 0 1 0 1 0 ? bit [7:0] ? csma_seed_0 the register bits csma_seed_0 contain the lower 8 bits of the csma_seed. the upper 3 bits are stored in register bits csma_seed_1 of register 0x2e (csma_seed_1). csma_seed is the seed of the random number generator for the csma-ca algorithm. register 0x2e (csma_seed_1) the csma_seed_1 register contains a fraction of the csma_seed value, the back- off exponent for the csma-ca algorithm and configuration bits for address filtering in rx_aack operation. bit 7 6 5 4 0x2c min_be aack_set_pd reserved csma_seed_1 read/write r/w r/w r/w r reset value 1 1 0 0 bit 3 2 1 0 0x2c i_am_coord csma_seed_1 csma_seed_1 read/write r/w r/w r/w r/w reset value 0 0 1 0 ? bit [7:6] ? min_be the register bit min_be defines the minimal back-off exponent used in the csma-ca algorithm to generate a pseudo random number for back-off the cca. for details refer to ieee 802.15.4-2003 section 7. 5.1.3. if set to zero, the st art of the cca algorithm is not delayed. ? bit 5 ? aack_set_pd this register bit defines the content of t he frame pending subfield for acknowledgement frames in rx_aack mode. if this bit is enabled the frame pending subfield of the
42 5131e-mcu wireless-02/09 at86rf230 acknowledgment frame is set in response to a mac command data request frame, otherwise not. the register bit has to be se t before finishing the shr transmission of the acknowledgment frame. this is 352 s (192 s ack wait time + 160 s shr transmission) after the trx_end interrupt issued by the frame to be acknowledged. ? bit 4 ? reserved ? bit 3 ? i_am_coord this register bit has to be set if the node is a pan coordinator. this register bit is used for address filtering in rx_aack. if i_am_coord = 1 and if only source addressing fields are included in a data or mac command frame, the frame shall be accepted only if the device is the pan coordinator and t he source pan identifier matches macpanid, for details refer to ieee 802. 15.4-2003, section 7. 5.6.2 (third-level filter rules). ? bit [2:0] ? csma_seed_1 the register bits csma_seed_1 contain the upper 3 bits of the csma_seed. the lower part is defined in re gister 0x2d (csma_seed_0). 7.2.7 register description ? address registers regis ter 0x20 (short_addr_0) this register contains bits [7:0] of t he 16 bit short address for address filtering. bit 7 6 5 4 3 2 1 0 0x20 short_address_0 short_addr_0 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0 register 0x21 (short_addr_1) this register contains bits [15:8] of t he 16 bit short address for address filtering. bit 7 6 5 4 3 2 1 0 0x21 short_address_1 short_addr_1 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0 register 0x22 (pan_id_0) this register contains bits [7:0] of the 16 bit pan id for address filtering. bit 7 6 5 4 3 2 1 0 0x22 pan_id_0 pan_id_0 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0 register 0x23 (pan_id_1) this register contains bits [15:8] of the 16 bit pan id for address filtering. bit 7 6 5 4 3 2 1 0 0x23 pan_id_1 pan_id_1 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0
43 5131e-mcu wireless-02/09 at86rf230 register 0x24 (ieee_addr_0) this register contains bits [7:0] of the 64 bit ieee address fo r address filtering. bit 7 6 5 4 3 2 1 0 0x24 ieee_addr_0 ieee_addr_0 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0 register 0x25 (ieee_addr_1) this register contains bits [15:8] of t he 64 bit ieee address for address filtering. bit 7 6 5 4 3 2 1 0 0x25 ieee_addr_1 ieee_addr_1 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0 register 0x26 (ieee_addr_2) this register contains bits [23:16] of t he 64 bit ieee address for address filtering. bit 7 6 5 4 3 2 1 0 0x26 ieee_addr_2 ieee_addr_2 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0 register 0x27 (ieee_addr_3) this register contains bits [31:24] of t he 64 bit ieee address for address filtering. bit 7 6 5 4 3 2 1 0 0x27 ieee_addr_3 ieee_addr_3 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0 register 0x28 (ieee_addr_4) this register contains bits [39:32] of t he 64 bit ieee address for address filtering. bit 7 6 5 4 3 2 1 0 0x28 ieee_addr_4 ieee_addr_4 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0 register 0x29 (ieee_addr_5) this register contains bits [47:40] of t he 64 bit ieee address for address filtering. bit 7 6 5 4 3 2 1 0 0x29 ieee_addr_5 ieee_addr_5 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0
44 5131e-mcu wireless-02/09 at86rf230 register 0x2a (ieee_addr_6) this register contains bits [55:48] of t he 64 bit ieee address for address filtering. bit 7 6 5 4 3 2 1 0 0x2a ieee_addr_6 ieee_addr_6 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0 register 0x2b (ieee_addr_7) this register contains bits [63:56] of t he 64 bit ieee address for address filtering. bit 7 6 5 4 3 2 1 0 0x2b ieee_addr_7 ieee_addr_7 read/write r/w r/w r/w r/w r/w r/w r/w r/w reset value 0 0 0 0 0 0 0 0
45 5131e-mcu wireless-02/09 at86rf230 8 functional description 8.1 introduction - frame format figure 8-1 provides an overview of the physical layer frame structure as defined by the ieee 802.15.4-2003 standard. figure 8-2 shows details of the defined mac layer frame stru cture. figure 8-1 ieee 802.15.4-2003 frame format ? phy layer frame structure figure 8-2 ieee 802.15.4-2003 frame format ? mac layer frame structure 8.1.1 phy protocol layer data unit (ppdu) 8.1.1.1 synchroni zation header (shr) the shr consists of a four-octet preamble fi eld (all zero), followed by a single sfd octet which has the predefined value 0xa7. when transmitting, the shr is automatically generated by the at86rf230, and prefixed to the frame that has been read from the frame buffer. the transmission of the shr requires 160 s (10 symbols). this allows the microcontroller to initiate a transmission and to start downloading the frame contents subsequently. note, that in this case the spi transfer rate must be equal or faster than the phy data rate. during frame reception, the shr is used fo r phy synchronization purposes. in basic operating mode an rx_start interrupt is issued 8 s after detection of the sfd field.
46 5131e-mcu wireless-02/09 at86rf230 8.1.1.2 phy header (phr) the phy header consists of a single octet following the shr. the least significant 7 bits of that octet denote the frame lengt h of the following psdu, while the most significant bit of that octet is reserved. during transmission, the phr field has to be supplied by the microcontroller during frame buffer write access. on receive, the radio transceiver does not write the phr field into the frame buffer. instead it is prefixed to the psdu during fr ame buffer read access. note, that the reserved msb of the phr octet is always set to 0. 8.1.1.3 phy payload (phy service data unit, psdu) the psdu has a variable length between one and 127 octets. 8.1.2 mac protocol layer data unit (mpdu) 8.1.2.1 mac he ader (mhr) fields the mac header consists of the frame cont rol field (fcf), a sequence number, and the variable length addressing fields. 8.1.2.2 frame control field (fcf) the fcf consists of 16 bits, and occupies the first two octets of the mpdu. bit [2:0] describe the frame type. table 8-1 summarizes frame types defined by ieee 802.15.4-2003, section 7.2.1.1.1. table 8-1. ieee 802.15.4-2003 frame types frame control field bit assignments bit [2:0] value description 000 0 beacon 001 1 data 010 2 acknowledge 011 3 mac command 100 ? 111 4 ? 7 reserved these bits are used for address filtering by applying the ieee 802.15.4-2003 third level filter rules. only frame types 0 ? 3 pass t he third level filter rules. automatic address filtering by the at86rf230 is enabled when using the rx_aack operation (see section 7.2.3.1). bit 3: indicates whether security processing applies to this frame. this field is not evaluated by the at86rf230. bit 4 is the ?frame pending? subfield. this field can be set in an acknowledgement frame. it indicates that the transmitter of the acknowledgement frame has more data to send for the recipient of the acknowledgement frame. for acknowledgment frames automatically generated by the at 86rf230, this bit is set according to the content of register bit aack_set_pd in register 0x2e (csma_seed_1). bit 5 forms the ?acknowledgment request? subfield . if this bit is set within a data or mac command frame that is not broadcast, the recipient shall acknowledge the reception of the frame within the time specified by ieee 802.15.4-2003 (i.e. within 192 s for
47 5131e-mcu wireless-02/09 at86rf230 nonbeacon-enabled networks). the at86rf230 parses this bit during rx_aack operation and transmits an acknowledgment frame if necessary. bit 6 the ?intra-pan? subfield indicates that in a frame, where both, the destination and source addresses are present, the pan id is omitted from the source address field. this bit is evaluated by the at86rf230 address filter logic when using rx_aack operation. bit [11:10] the ?destination address mode? subf ield describes the format of the destination address of the frame. the values of the address modes are summarized in table 8-2, according to ieee 802.15.4-2003: table 8-2. ieee 802.15.4-2003 address modes addressing mode value bit [11:10] bit [15:14] value description 00 0 address not present 01 1 reserved, must not be used 10 2 address is 16-bit short 11 3 address is 64-bit extended address if the destination address mode is either 2 or 3 (i.e. if the destination address is present at all), it always consists of a 16-bit pan id first, followed by either the 16-bit or 64-bit address as described by the mode. bit [15:14] form the ?source address mode? subfield, with a similar meaning as ?destination address mode?. the address field description bits of the fc f (bits 6, 10, 11, 14, 15) affect the address filter logic of the at86rf230 while ope rating in rx_aack states (see section 7.2.3.1). 8.1.2.3 sequence number the one-octet sequence number following the fcf identifies a particular frame, so that duplicated frame transmissions can be detecte d. while operating in rx_aack states, the content of this field is copied from the frame to be acknowledged into the acknowledgment frame. 8.1.2.4 addressing fields the addressing fields terminate the mhr. the destination address (if present) is always transmitted first, followed by the source addres s (if present). each address consists of the pan id and a device address. if both ad dresses are present, and the ?intra pan? subfield in the fcf is set to 1, the source pan id is omitted. note that in addition to these general rule s, ieee 802.15.4-2003 further restricts the valid address combinations for the individual possible mac frame types. for example, the situation where both addresses are omitted (source addressing mode = 0 and destination addressing mode = 0) is only allowed for acknowledgment frames. the address filter in the at86rf230 has been designed to apply to ieee 802.15.4-2003 compliant frames only. 8.1.2.5 mac service data unit (msdu) this is the actual mac payload. it is usually structured according to the individual frame type descriptions in ieee 802.15.4-2003.
48 5131e-mcu wireless-02/09 at86rf230 8.1.2.6 mac footer (mfr) fields the mac footer consists of a two-octet frame checksum (fcs). the at86rf230 can generate and evaluate this fcs automatically, for details refer to section 8.2. 8.2 frame check sequence (fcs) the frame check sequence main features are: ? indicates bit errors, based on a cyclic redundancy check (crc) of length 16 bit ? uses international telecommunication union (itu) crc polynomial ? automatically evaluated during reception ? can be automatically generated during transmission 8.2.1.1 overview the fcs is intended for use at the mac level to detect corrupted frames. it is computed by applying an itu crc polynomial to all transferred bytes following the length field (mhr and msdu fields). the frame check sequence has a length of 16 bit and is located in the last two bytes of a frame (mac footer, see figure 8-2). the at8 6rf230 applies an fcs check on each received frame. the fcs check result is stored to register bit rx_crc_valid in register 0x06 (phy_rssi). on transmit the radio transceiver can be configured to autonomously compute and append the fcs bytes. 8.2.2 crc calculation the crc polynomial used in ieee 802.15.4-2003 networ ks is defined by 1 )( 51216 16 +++= xxxxg . the fcs shall be calculated for transmission using the following algorithm: let 1 2 2 1 1 0 )( ? ? ? ? ++++= k k k k bxbxbxbxm k be the polynomial representing the sequence of bits for which the checksum is to be computed. multiply m(x) by x 16 , giving the polynomial 16 )()( xxmxn ?= . divide n(x) modulo 2 by the generator polynomial, g 16 (x) , to obtain the remainder polynomial, 15 14 14 1 15 0 ... )( rxrxrxrxr ++++= the fcs field is given by the coefficients of the remainder polynomial, r(x) . example: considering a 5 octet ack frame. the mhr field consists of 0100 0000 0000 0000 0101 0110. the leftmost bit (b 0 ) is transmitted first in time. the fcs would be following 0010 0111 1001 1110. the leftmost bit (r 0 ) is transmitted first in time.
49 5131e-mcu wireless-02/09 at86rf230 8.2.3 automatic fcs generation the at86rf230 automatic fcs generation and insertion is enabled by setting register bit tx_auto_crc_on to 1. for a frame with a frame length field (phr) specified as n (3 n 127), the fcs is calculated on the first n -2 psdu octets in the frame bu ffer, and the resulting 16 bit fcs field is appended during transmission. note, if the at86rf230 automatic fcs generation is enabled, the frame download to the frame buffer can be stopped right after mac payload. there is no need to download fcs dummy bytes. in rx_aack states, when a received frame needs to be acknowledged, the fcs of the ack frame is always automatically generated by the at86rf230. example: a frame transmission of length five with the register bit tx_auto_crc_on set, is started with a frame download of five bytes (the last two bytes can be omitted). the first three bytes are used for fcs generation, the last two bytes are replaced by the internally calculated fcs. 8.2.4 automatic fcs check an fcs check is applied on each incoming frame with a frame length n 2. the result of the fcs check is stored to register bit rx_crc_valid in register 0x06 (phy_rssi). the register bit is updated at the event of the trx_end interrupt and remains valid until the next trx_end interrupt caused by a new frame reception. in rx_aack states, if fcs of the received frame is not valid, the radio transceiver rejects the frame and the trx_end interrupt will not be generated. in tx_aret states, the fcs of an ack is autom atically checked. if it is not correct, the ack is not accepted. 8.2.5 register description r egister 0x05 (phy_tx_pwr) the phy_tx_pwr register sets the transmit power and controls the fcs algorithm for tx operation. bit 7 6 5 4 0x05 tx_auto_crc_on reserved phy_tx_pwr read/write r/w r r r reset value 0 0 0 0 bit 3 2 1 0 0x05 tx_pwr phy_tx_pwr read/write r/w r/w r/w r/w reset value 0 0 0 0 ? bit 7 ? tx_auto_crc_on register bit tx_auto_crc_on controls the automatic fcs generation for tx operation. the automatic fcs algorithm is performed autonomously by the radio transceiver if register bit tx_auto_crc_on = 1. ? bit [6:4] ? reserved ? bit [3:0] ? tx_pwr refer to section 9.2.3.
50 5131e-mcu wireless-02/09 at86rf230 register 0x06 (phy_rssi) the phy_rssi register is a multi purpose r egister to indicate the current received signal strength (rssi) and the fcs validity of a received frame. bit 7 6 5 4 0x06 rx_crc_valid reserved rssi phy_rssi read/write r r r r reset value 0 0 0 0 bit 3 2 1 0 0x06 rssi phy_rssi read/write r r r r reset value 0 0 0 0 ? bit 7 ? rx_crc_valid this register bit indicates whether a received frame has a valid fcs. the register bit is updated when issuing the trx_end interrupt remains valid until the next trx_end interrupt caused by a new frame reception. table 8-3. rx fcs result register bit value description 0 fcs is not valid. rx_crc_valid 1 fcs is valid. ? bit [6:5] ? reserved ? bit [4:0] ? rssi refer to section 8.4.4. 8.3 energy detection (ed) the main features for the energy detection module are: ? 85 unique energy levels defined ? 1 db resolution 8.3.1 overview the receiver energy detection measurement is used by a network layer as part of a channel selection algorithm. it is an estimation of the received signal power within the bandwidth of an ieee 802.15.4-2 003 channel. no attempt is made to identify or decode signals on the channel. the ed value is calculated by averaging rssi values over eight symbols (128 s). 8.3.2 request an ed measurement there are two ways implemented in the at86rf230 to initiate an ed measurement: ? manually, by a write access to r egister 0x07 (phy_ed_level), or ? automatically, by detecting a valid sfd of an incoming frame. for manually initiated ed measurement the radio transceiver needs to be in one of the states rx_on or busy_rx. an automated ed measurement is started, if a sfd field is detected. a valid sfd detection is signalized by an rx_start interrupt in basic operating mode.
51 5131e-mcu wireless-02/09 at86rf230 the measurement result is stored to regi ster 0x07 (phy_ed_level) 140 s after its initialization. the value is always 0 if the at86rf230 is not in any of the rx states. thus by using basic operating mode, a va lid ed value from the currently received frame is accessible 140 s after the rx_start interrupt and remains valid until a new rx_start interrupt is generated by the next incoming frame or until another ed measurement is initiated manually. by using the extended operating mode, the rx_start interrupt is always masked and cannot be used as timing reference. here successful frame reception is only signalized by the trx_end interrupt. the minimum time between a trx_end interrupt and a following sfd detection is 96 s. including the ed measurement time, the ed value needs to be read within 224 s after the trx_end interrupt; otherwise, it could be overwritten by the result of the next measurement cycle. note, it is not recommended to initiate manually an ed measurement when using the extended operating mode. 8.3.3 data interpretation the phy_ed_level is an 8 bit register. the ed value of the at86rf230 radio transceiver has a valid range from 0 to 84 with a resolution of 1 db. all other values do not occur. if zero is read from the phy_ed _level register, this indicates that the measured energy is less than -91 dbm (see parameter 11.7.16). due to environmental con ditions (temperature, volt age, semiconductor parameters, etc.) the computed energy value has an accuracy of 5 dbm, this is to be considered as constant offset over the measurement range. 8.3.4 register description register 0x07 (phy_e d_level) the ed_level register contains the result after an ed measurement. bit 7 6 5 4 3 2 1 0 0x07 ed_level[7:0] ed_level read/write r r r r r r r r reset value 0 0 0 0 0 0 0 0 ? bit [7:0] ? ed_level the minimum ed value (ed_level = 0) indicates receiver power less than rssi_base_val. the range is 84 db with a resolution of 1 db and an absolute accuracy of 5 db. the measurement period is 8 symbol periods. a manual ed measurement can be initiated by a write access to the register. 8.4 received signal strength indicator (rssi) the received signal strength indicator main features are: ? minimum rssi sensitivity is -91 dbm (rssi_base_val, see parameter 11.7.16) ? dynamic range is 81 db ? minimum rssi value is 0 ? maximum rssi value is 28
52 5131e-mcu wireless-02/09 at86rf230 8.4.1 overview the rssi is a 5-bit value indicating the receive power in the selected channel, in steps of 3 db. no attempt is made to distingui sh between ieee 802.15.4 signal and other signal source, only the received signal power is evaluated. the rssi provides the basis for ed measurement. 8.4.2 reading rssi using the basic operating mode, the rssi value is valid at any rx state, and is updated every 2 s. the current rssi value is stored to the phy_rssi register. note, it is not recommended to read the rssi value when using the extended operating mode. the automatically generated ed value should be used alternatively (see section 8.3). 8.4.3 data interpretation the phy_rssi is an 8-bit register, however, the value is represented in the lowest five bits [4:0] and the range is 0 ? 28. an rssi value of 0 indicates an rf input power of < -91 dbm. for an rssi value in the range of 1 to 28, the rf input power can be calculated as follows: p rf = rssi_base_val + 3?(rssi - 1) 8.4.4 register description r egister 0x06 (phy_rssi) the phy_rssi register is a multi purpose r egister to indicate the current received signal strength (rssi) and the fcs validity of a received frame. bit 7 6 5 4 0x06 rx_crc_valid reserved rssi phy_rssi read/write r r r r reset value 0 0 0 0 bit 3 2 1 0 0x06 rssi phy_rssi read/write r r r r reset value 0 0 0 0 ? bit 7 ? rx_crc_valid refer to section 8.2.5. ? bit [6:5] ? reserved ? bit [4:0] ? rssi the register bits rssi contain the resu lt of the automated rssi measurement. the value is updated every 2 s in receive states. the read value is a number between 0 and 28 indicating the received signal strength as a linear curve on a logarithmic input power scale (dbm) with a resolution of 3 db. an rssi value of 0 indicates an rf input power of < -91 dbm (see parameter 11.7.17), a value of 28 a power of -1 0 dbm (see parameter 11.7.18).
53 5131e-mcu wireless-02/09 at86rf230 8.5 link quality indication (lqi) the ieee 802.15.4 standard defines the lqi m easurement as a characterization of the strength and/or quality of a received packet. the use of the lqi result by the network or application layer is not specified in this standard. lqi values shall be an integer ranging from 0 to 255. the minimum and maximum lqi values (0 and 255) should be associated with the lowest and highest quality compliant signals, respectively, and lqi values in between should be uniformly distributed between these two limits. 8.5.1 overview the at86rf230 determines the link quality of a radio link. the radio transceiver uses correlation results of multiple symbols within a frame to determine the lqi value. this is done for each received frame. the minimum frame length for a valid lqi value is two octets psdu. lqi values are integers ranging from 0 to 255. the lqi values can be associated with an ex pected packet error rate (per). the per is the ratio of erroneous received frames to the total number of received frames. a per of zero indicates no frame error, whereas at a per of one no frame was received correctly. as an example, figure 8-3 shows the conditional packet error rate with associated lqi values. t he values are taken from received frames of length 20 octets psdu on transmission channels with low multipath delay spreads. even if the transmission channel characteristic has higher multipath delay spread than assumed for this example, the dependency of per to lqi values is not affected. since the packet error rate is a statistical value, the per shown in figure 8-3 is based on a hug e number of receptions. figure 8-3. conditional packet error rate versus lqi 0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1 0 50 100 150 200 250 per lqi 8.5.2 request an lqi measurement the lqi byte can be obtained after a frame has been received by the radio transceiver. one additional byte is attached to the received frame containing the lqi value. this
54 5131e-mcu wireless-02/09 at86rf230 information can be read as an extra byte from the frame buffer (see section 9.1). the lqi byte can be uploaded after the trx_end interrupt. 8.5.3 data interpretation a low lqi value is associated with low signal strength and/or high signal distortions. signal distortions are mainly caused by interference signals and/or multipath propagation. high lqi values indicate a sufficient high signal power and low signal distortions. note, the received signal power as indicated by received signal strength indication (rssi) value or energy detection (ed) value do not characterize the signal quality and the ability to decode a signal. as an example, a received signal with an input power of about 6 db above the receiver sensitivity likely results in a lqi value close to 255 for radio channels with very low signal distortions. for higher signal power levels the lqi value becomes independent of the actual signal strength. this is because the packet error rate for these scenarios tends towards zero and further increase of the signal strength, i.e. by increasing the transmissi on power, does not decrease the error rate any further. in this case rssi or ed can be used to evaluate the signal strength and the link margin. zigbee networks require to determine the ?best? route between two nodes. both, the lqi and the rssi/ed can be used for this, depending on the optimization criteria. as a rule of thumb rssi/ed is useful to differentiate between links with high lqi values. transmission links with low lqi values should be discarded for routing decisions even if the rssi/ed values are high. 8.6 clear channel assessment (cca) the main features of the clear c hannel assessment (cca) module are: ? all 3 modes available as defined by ieee 802.15.4-2003 in section 6.7.9 ? adjustable threshold of the energy detection algorithm 8.6.1 overview the cca is used to detect a clear channel. there are three modes available as defined in table 8-4. table 8-4. available cca modes cca mode description 1 energy above threshold. cca shall report a busy medium upon detecting any energy above the ed threshold. 2 carrier sense only. cca shall report a busy medium only upon the detection of a signal with the modulation and spreading characteristics of ieee 802.15.4. this signal may be above or below the ed threshold. 3 carrier sense with energy above threshold. cca shall report a busy medium only upon the detection of a signal with the modulation and spreading characteristics of ieee 802.15.4 with energy above the ed threshold.
55 5131e-mcu wireless-02/09 at86rf230 8.6.2 cca configuration and request the cca modes are configurable via register 0x08 (phy_cc_cca). the 4 bit value cca_ed_thres of register 0x09 (cca_thres) defines the received power threshold of the ?energy above threshold? algorithm. the threshold is calculated by rssi_base_val+2?cca_ed_thres [dbm]. using the basic operating mode, a cca request can be initiated manually by setting cca_request = 1 in register 0x08 (phy_c c_cca), if the at86rf230 is in any rx state. the cca computation is done over eight symbol periodes and the result is accessible 140 s after the request. note, it is not recommended to initiate manually a cca measurement when using the extended operating mode. 8.6.3 data interpretation the current channel status (cca_statu s) and the cca completion status (cca_done) are accessible in register 0x01 (trx_status). note, a read access to this register clears register bits cca_done and cca_status. the completion of a measurement cycle is indicated by cca_done = 1. if the radio transceiver detected no signal (idle cha nnel) during the measurement cycle, the cca_status bit is set to 1. when using the ?energy above threshold? algorithm (mode 1 and mode 3) any received power above cca_ed_thres level is interpreted as a busy channel. the ?carrier sense? algorithm (mode 2 and mode 3) reports a busy channel when detecting a ieee 802.15.4 signal above the rssi_base_val (see parameter 11.7.16). the radio transceive r is also able to detect signals below this value, but the detection probability decreases with the signal power. it is almost zero at the radio transceivers sensitivity level (see parameter 11.7.1). 8.6.4 register description regis ter 0x01 (trx_status) the trx_status register signals the current state of the radio transceiver as well as the status of the cca measurement. note, a r ead access to the register clears bits cca_done and cca_status. bit 7 6 5 4 0x01 cca_done cca_status reserved trx_status trx_status read/write r r r r reset value 0 0 0 0 bit 3 2 1 0 0x01 trx_status trx_status read/write r r r r reset value 0 0 0 0 ? bit 7 ? cca_done this register indicates if a cca request is completed. each read access to register 0x01 resets the cca_done bit.
56 5131e-mcu wireless-02/09 at86rf230 table 8-5. status cca algorithm register bit value description 0 cca calculation in progress cca_done 1 cca calculation finished ? bit 6 ? cca_status cca_status register bit indicates the result of a cca request. each read access to register 0x01 resets the cca_status bit. table 8-6. status cca result register bit value description 0 channel is busy cca_status 1 channel is idle ? bit 5 ? reserved ? bit [4:0] ? trx_status refer to section 7.1.5. register 0x08 (phy_cc_cca) the phy_cc_cca register contains register bits to initiate and control the cca measurement as well as to set the channel center frequency. bit 7 6 5 4 0x08 cca_request cca_mode channel phy_cc_cca read/write r/w r/w r/w r/w reset value 0 0 1 0 bit 3 2 1 0 0x08 channel phy_cc_cca read/write r/w r/w r/w r/w reset value 1 0 1 1 ? bit 7 ? cca_request a manual cca measurement is initiated with setting cca_request = 1. ? bit [6:5] ? cca_mode the cca mode can be selected using register bits cca_mode. table 8-7. cca modes register bit value description 0 reserved 1 mode 1, energy above threshold 2 mode 2, carrier sense only cca_mode 3 mode 3, carrier sense with energy above threshold ? bit [4:0] ? channel refer to section 9.7.5.
57 5131e-mcu wireless-02/09 at86rf230 register 0x09 (cca_thres) this register contains the thre shold level for cca-ed measurement. bit 7 6 5 4 0x09 reserved cca_thres read/write r/w r/w r/w r/w reset value 1 1 0 0 bit 3 2 1 0 0x09 cca_ed_thres cca_thres read/write r/w r/w r/w r/w reset value 0 1 1 1 ? bit [7:4] ? reserved ? bit [3:0] ? cca_ed_thres the register bits cca_ed_thres define the threshold value of the cca-ed measurement. a cannel is indicated as bus y when the received signal power is above rssi_base_val + 2 ? cca_ed_thres [dbm].
58 5131e-mcu wireless-02/09 at86rf230 9 module description 9.1 receiver (rx) 9.1.1 overview the at86rf230 receiver is spitted into an analog radio front end and a digital base band processor (rx bbp), see figure 3-1. the rf signal is amplified by a low noise amplifier (lna) and converted down to an intermediate frequency by a mixer. channel selectivity is performed using an integrated band pass filter. a limiting amplifier (limiter) provides sufficient gain to overcome the dc offset of the succeeding analog-to-digital converter (adc) and generates a digital rssi signal with 3 db granularity. the if signal is sampled and processed further by the digital base band receiver. the rx bbp performs additional signal filtering and signal synchronization. the frequency offset of each frame is calculat ed by the synchronization unit and is used during the remaining receive process to correct the offset. the receiver is designed to handle frequency and symbol rate deviations up to 120 ppm, caused by combined receiver and transmitter deviations. for details refer to section 11.5 parameter 11.5.6. finally the sig nal is demodulated and the data are stored to the frame buffer. in basic operating mode the start of an i eee 802.15.4 compliant frame is indicated by a rx_start interrupt. accordingly it?s en d is signalized by an trx_end interrupt. based on the quality of the received signal a link quality indicator (lqi) is calculated and appended to the frame, refer to section 8.5. additional signal processing is applied to the fra me data to provide further status information like ed value (register 0x07) and fcs correctness (register 0x06). beyond these features the extended oper ating mode of the at86rf230 supports address filtering and pending data indication. for details refer to section 7.2. 9.1.2 configuration the receiver is enabled by writing the command rx_on for the basic operating mode or rx_aack_on for the extended operating mode to register bits trx_cmd in register 0x02 (trx_state). the receiver does not need any additional configuration to receive ieee 802.15.4 compliant frames on the current selected channel when using the basic operating mode. however the frame reception in t he extended operating mode requires further register configurations, for details refer to section 7.2. 9.2 transmitter (tx) 9.2.1 overview the at86rf230 transmitter consists of a digital base band processor (tx bbp) and an analog radio front end, see figure 3-1. the tx bbp reads the frame data from t he fram e buffer and performs the bit-to- symbol and symbol-to-chip mapping as spec ified by ieee 802.15.4 in section 6.5.2. the o-qpsk modulation signal is generated and fed into the analog radio front end. the fractional-n frequency synthesizer (pll) converts the baseband transmit signal to the rf signal, which is amplified by the power amplifier (pa). the pa output is internally
59 5131e-mcu wireless-02/09 at86rf230 connected to bidirectional differential antenn a pins (rfp, rfn), so that no external antenna switch is needed. 9.2.2 configuration in basic operating mode a transmission is st arted from pll_on state by either writing tx_start to register bits trx_cmd (register 0x02, trx_state) or by raising edge of slp_tr. in extended operating modes a transmission is started automatically dependent on the transaction phase of either rx_aac k or tx_aret, refer to section 7.2. the rf output power can be set via r egister bits tx_pwr in register 0x05 (phy_tx_pwr). the maximum output power of the transmitter is typical +3 dbm. the selectable output power range of the transmitter is 20 db. 9.2.3 register description r egister 0x05 (phy_tx_pwr) the phy_tx_pwr register sets the transmit power and controls the fcs algorithm for tx operation. bit 7 6 5 4 0x05 tx_auto_crc_on reserved phy_tx_pwr read/write r/w r r r reset value 0 0 0 0 bit 3 2 1 0 0x05 tx_pwr phy_tx_pwr read/write r/w r/w r/w r/w reset value 0 0 0 0 ? bit 7 ? tx_auto_crc_on refer to sections 7.2.6 and 8.2. ? bit [6:4] ? reserved ? bit [3:0] ? tx_pwr the register bits tx_pwr sets the tx out put power of the at86rf230. the available power settings are summarized in table 9-1. table 9-1. pa output power setting register bits value [3 :0] output power [dbm] 0x0 +3.0 0x1 +2.6 0x2 +2.1 0x3 +1.6 0x4 +1.1 0x5 +0.5 0x6 -0.2 0x7 -1.2 0x8 -2.2 0x9 -3.2 tx_pwr 0xa -4.2
60 5131e-mcu wireless-02/09 at86rf230 register bits value [3 :0] output power [dbm] 0xb -5.2 0xc -7.2 0xd -9.2 0xe -12.2 0xf -17.2 9.3 frame buffer the at86rf230 contains a 128 byte dual port sram. one port is connected to the spi interface, the other to the internal tx/rx bbp port. for data communication both ports are independent and simultaneously accessible. access conflicts are indicated by a trx under run (trx_ur) interrupt. the frame buffer is used for the tx and rx operation of the device and can keep one ieee 802.15.4-2003 tx or one rx frame of maximum length at a time. note, a frame buffer access is only possible if the digital voltage regulator is turned on. this is the case in all device states except in sleep and p_on. 9.3.1 frame buffer data management data stored in frame buffer (received data or data to be transmitted) remains valid as long as ? no new frame is written into the buffer via spi ? no new frame is received (in any busy_rx state) ? no state change into sleep state is made if the radio transceiver is in any rx state an incoming frame with valid sfd field overwrites the frame buffer content 32 s a fter the rx_start inte rrupt occurs, even if the rx_start interrupt is disabled. thus the frame buffer content should be uploaded to the microcontroller before the next sfd is received. to avoid an unintended frame buffer overwrite a state change to pll_on immediately after the frame reception (trx_end interrupt) is recommended. using the extended operating mode stat es tx_aret_on or tx_aret_on_noclk, the radio transceiver switches to rx (afte r successful frame transmission), if an acknowledgement was requested in fcf. re ceived frames are evaluated but not stored in the frame buffer in these states. th is allows the radio transceiver to wait for an acknowledgement frame and retry the data frame transmission without downloading them again. a radio transceiver state cha nge, except a transition to sleep, does not affect the frame buffer contents. if the radio transceiver is forced into sleep, the frame buffer is powered off and the stored data gets lost. 9.3.2 user accessible frame content the at86rf230 supports an i eee 802.15.4-2003 compliant frame format as shown in figure 9-1.
61 5131e-mcu wireless-02/09 at86rf230 figure 9-1. frame structure a frame comprises two sections, the fixed internally generated shr field and the user accessible part stored in the frame buffer. t he first fixed part of the frame consists of the preamble and the sfd field. the variable frame section contains the frame length field and the frame payload followed by the fcs field. the frame buffer content differs depending on the direction of the communication (rx or tx). to access the data follow the procedures described in sections 6.2.2 and 6.2.3. in any of the receive state s, the payload and the link quality indicator (lqi) value of a successfully received frame are stored to the frame buffer. the radio transceiver appends the lqi value to the psdu data. the fr ame length information is not stored to the frame buffer. when using the frame buffer access mode to read the frame buffer content, the phr octet is automatically prefixed to the payload during the upload process. if the sram access mode is used, the frame length information cannot be accessed. the preamble or the sfd value cannot be read. for frame transmission, the phr octet and the psdu data shall be stored to the frame buffer. if the tx_auto_crc_on bit is set in register 0x05 (phy_tx_pwr), the fcs field is replaced by the automatically calc ulated fcs during frame transmission. there is no need to download the fcs field when using the automatic fcs generation. for non ieee 802.15.4-2003 frames, the mi nimum psdu length supported by the at86rf230 is one byte. 9.3.3 frame buffer interrupt handling access conflicts may occur when reading or writing data simultaneously at the two independent ports of the frame buffer, bbp and spi. both of these ports have its own address counter that points to t he frame buffer?s current address. during frame buffer read access, if the spi port?s address counter value is more than or equal to that of tx/rx bbp port then an access violation occurs. this indicates that the spi transfer rate is higher than the phy data rate. similar on frame buffer write access, an access violation occurs if the spi port?s address counter value is less than or equal to that of tx/rx bbp port. this access violation can occur if the spi transfer rate during a frame download is slower than the phy data rate, while having started the frame transmission already. both these access violations may cause data corruption and are indicated by trx_ur interrupt when using the frame buffer access mode. access violations are not indicated when using the sram access mode. while receiving a frame, primarily the data needs to be stored to the frame buffer before reading it. this can be ensured by star ting the frame buffer read access 32 s after the rx_start interrupt at the earli est. when reading the frame data continuously
62 5131e-mcu wireless-02/09 at86rf230 the spi transfer rate shall be lower than 250 kbit/s to ensure no trx_ur interrupt occurs. note, during the frame buffer read access the trx_ur interrupt is first valid 64 s after the rx_start interrupt. the occurrence of the interrupt can be disregarded when reading the first byte of the frame buffer between 32 s and 64 s after the rx_start interrupt. if a received frame upload is delayed and during the upload process a new frame is received, a trx_ur and an rx_start inte rrupt occurs. even so, the old frame data can be read, if the spi data rate is higher than the effective over air data rate. a minimum spi clock rate of 1 mhz is recommended in this special case. finally it is required to check the uploaded frame data int egrity by a fcs using the microcontroller. when writing data to the frame buffer during frame transmission, the spi transfer rate shall be higher than 250 kbit/s to ensure no trx_ur interrupt occurs. the first byte of the psdu data must be available in the frame buffer before sfd transmission has been completed, which takes 176 s (16 s pa ramp up + 128 s preamble transmission + 32 s sfd transmission) from the rising edge of slp_tr pin (see figure 7-2). 9.4 voltage regulators (avreg, dvreg) the main features of the voltage regulator modules are: ? bandgap stabilized 1.8v supply for analog and digital domain. ? low dropout (ldo) voltage regulator ? configurable for usage of external voltage regulator 9.4.1 overview the internal voltage regulators supply the low voltage domains of the at86rf230. the avreg provides the regulated 1.8v supply voltage for the analog section and the dvreg supplies the 1.8v supply voltage for the digital section. a simplified schematic of the internal voltage regulator is shown in figure 9-2. figure 9-2. simplified schematic of avreg/dvreg bandgap voltage reference 1.25v dvdd / avdd devdd / evdd
63 5131e-mcu wireless-02/09 at86rf230 9.4.2 configure the voltage regulators the voltage regulators can be configured by the register 0x10 (vreg_ctrl). it is recommended to use the internal regulators, but it is also possible to supply the low voltage domains by an external voltage source. for this configuration, the internal regulators need to be switched off by setting the register bits to the values avreg_ext = 1 and dvreg_ext = 1. a regulated external supply voltage of 1.8v needs to be connected to the pins dvdd and avdd. when turning on the external supply, ensure a sufficiently long stabilization time before interacting with the at86rf230. 9.4.3 data interpretation the status bit values avdd_ok = 1 and dv dd_ok = 1 indicate an enabled and stable internal supply voltage. reading 0 indicates a disabled or unstable internal supply voltage. 9.4.4 register description regis ter 0x10 (vreg_ctrl) this register vreg_ctrl controls the use of the voltage regulators and indicates the status of these. bit 7 6 5 4 0x10 avreg_ext avdd_ok reserved vreg_ctrl read/write r/w r r/w r/w initial value 0 0 0 0 bit 3 2 1 0 0x10 dvreg_ext dvdd_ok reserved vreg_ctrl read/write r/w r r/w r/w initial value 0 0 0 0 ? bit 7 ? avreg_ext the register bit avreg_ext defines whether the internal analog voltage regulator or an external regulator is used to supply the analog low voltage building blocks of the radio transceiver. table 9-2. regulated voltage supply control for analog building blocks register bit value description 0 use internal voltage regulator avreg_ext 1 use external voltage regulator, internal voltage regulator is disabled ? bit 6 ? avdd_ok this register bit avdd_ok indicates if the internal 1.8v regulated supply voltage avdd has settled. the bit is set to logic high, if avreg_ext = 1. table 9-3 regulated voltage supply control for analog building blocks register bit value description 0 analog voltage regulator disabled or supply voltage not stable avdd_ok 1 analog supply voltage has settled
64 5131e-mcu wireless-02/09 at86rf230 ? bit [5:4] ? reserved ? bit 7 ? dvreg_ext the register bit dvreg_ext defines whether t he internal digital voltage regulator or an external regulator is used to supply the digital low voltage building blocks of the radio transceiver. table 9-4. regulated voltage supply control for digital building blocks register bit value description 0 use internal voltage regulator dvreg_ext 1 use external voltage regulator, internal voltage regulator is disabled ? bit 6 ? dvdd_ok this register bit dvdd_ok indicates if the internal 1.8v regulated supply voltage dvdd has settled. the bit is set to logic high, if dvreg_ext = 1. table 9-5 regulated voltage supply control for digital building blocks register bit value description 0 digital voltage regulator disabled or supply voltage not stable dvdd_ok 1 digital supply voltage has settled ? bit [1:0] ? reserved 9.5 battery monitor (batmon) the main features of the battery monitor are: ? programmable voltage threshold range: 1.7v to 3.675v ? battery low voltage interrupt 9.5.1 overview the battery monitor (batmon) detects and indicates a low supply voltage. this is done by comparing the voltage on the external supply pin (evdd) with a programmable internal threshold voltage. a simplified schematic of the batmon with the most important input and output signals is shown in figure 9-3. figure 9-3. simplified schematic of batmon batmon_hr batmon_vth 4 evdd threshold voltage batmon_ok ?1? batmon_irq for input-to-output mapping see control register 0x11 (batmon) dac + - d q clear
65 5131e-mcu wireless-02/09 at86rf230 9.5.2 data interpretation the signal bit batmon_ok of register 0x11 (batmon) indicates the current value of the battery voltage: ? if batmon_ok = 0, the battery voltage is lower than the threshold voltage ? if batmon_ok = 1, the battery voltage is higher than the threshold voltage after setting a new threshold, the value batmon_ok should be read out to verify the current supply voltage value. note, the battery monitor is inactive during p_on and sleep states, see control register 0x01 (trx_status). 9.5.3 batmon interrupt handling a supply voltage drop below the programmed threshold value is indicated by the bat_low interrupt, see control register 0x0e and 0x0f. the interrupt is issued only if batmon_ok changes from 1 to 0. no interrupt is generated when: ? the battery voltage is under the default 1.8v threshold at power up (batmon_ok was never 1), or ? a new threshold is set, which is still above the current supply voltage (batmon_ok remains 0). noise or temporary voltage drops may generate unwanted interrupts when the battery voltage is close to the programmed threshold voltage. to avoid this: ? disable the irq_7 (bat_low) in register 0x0e (irq_mask) and treat the battery as empty, or ? set a lower threshold value. 9.5.4 register description r egister 0x11 (batmon) the register batmon configures the battery monitor. additionally the supply voltage status at pin 28 (evdd) is accessible by reading register bit batmon_ok according to the actual batmon settings. bit 7 6 5 4 0x11 reserved batmon_ok batmon_hr batmon read/write r r r r/w reset value 0 0 0 0 bit 3 2 1 0 0x11 batmon_vth batmon read/write r/w r/w r/w r/w reset value 0 0 1 0 ? bit [7:6] ? reserved ? bit 5 ? batmon_ok the register bit batmon_ok indicates the level of the external supply voltage with respect to the programmed threshold batmon_vth.
66 5131e-mcu wireless-02/09 at86rf230 table 9-6. battery monitor status register bit value description 0 v dd < batmon_vth batmon_ok 1 v dd > batmon_vth ? bit 4 ? batmon_hr the register bit batmon_hr selects the range and resolution of the battery monitor. table 9-7. battery monitor voltage range settings register bit value description 0 enables the low range, see batmon_vth batmon_hr 1 enables the high range, see batmon_vth ? bit [3:0] ? batmon_vth the threshold value for the battery monitor is set with register bits batmon_vth. table 9-8. battery monitor threshold voltages value batmon_vth [3:0] threshold voltage [v] batmon_hr = 1 threshold voltage [v] batmon_hr = 0 0x0 2.550 1.70 0x1 2.625 1.75 0x2 2.700 1.80 0x3 2.775 1.85 0x4 2.850 1.90 0x5 2.925 1.95 0x6 3.000 2.00 0x7 3.075 2.05 0x8 3.150 2.10 0x9 3.225 2.15 0xa 3.300 2.20 0xb 3.375 2.25 0xc 3.450 2.30 0xd 3.525 2.35 0xe 3.600 2.40 0xf 3.675 2.45 9.6 crystal oscillator (xosc) the main crystal oscillator features are: ? 16 mhz amplitude controlled crystal oscillator ? 500 s typical settling time ? integrated trimming capacitance array ? programmable clock output (clkm)
67 5131e-mcu wireless-02/09 at86rf230 9.6.1 overview the crystal oscillator generates the reference frequency for the at86rf230. all other internally generated frequencies of the radio transceiver are derived from this unique frequency. therefore, the overall system per formance is mainly based on the accuracy of this reference frequency. the external co mponents of the crystal oscillator should be selected carefully and the related board layout should be done meticulously (refer to section 5). the re gister 0x12 (xosc_ctrl) provides access to the control signals of the oscillator. two operating modes are supported. it is recommended to use the integrated oscillator setup as described in figure 9-4, nevertheless a reference frequency can be fed to the internal ci rcuitry by using an external clock reference as shown in figure 9-5. 9.6.2 integrated oscillator setup using the internal oscillator, the oscillation frequency strongly depends on the load capacitance between the crystal pins xtal1 and xtal2. the total load capacitance cl must be equal to the specified load capacitance of the crystal itself. it consists of the external capacitors cx and parasitic capa citances connected to the xtal nodes. in figure 9-4, all parasitic capacitances, such as pcb stray capacitances and the pin input capacitance, are summarized to c par . additional internal trimming capacitors c trim are available. any value in the range from 0 pf to 4.5 pf with a 0.3 pf resolution is selectable using xtal_trim of register 0x 12 (xosc_ctrl). to calculate the total load capacitance, the following formula can be used cl = 0.5?(cx+c trim +c par ). the trimming capacitors provide the possibility of reducing frequency deviations caused by production process variations or by ex ternal components tolerances. note that the oscillation frequency can be reduced only by increasing the trimming capacitance. the frequency deviation caused by one step of c trim decreases with increasing crystal load capacitor values. a magnitude control circuit is included to ensure stable operation under different operating conditions and for different crysta l types. a high current during the amplitude build-up phase guarantees a low start-up time . at stable operation, the current is reduced to the amount necessary for a robust operation. this also keeps the drive level of the crystal low. generally, crystals with a higher load capacitance are less sensitive to parasitic pulling effects caused by external component variat ions or by variations of board and circuit parasitics. on the other hand, a larger crysta l load capacitance results in a longer start- up time and a higher steady state current consumption.
68 5131e-mcu wireless-02/09 at86rf230 figure 9-4. simplified xosc schematic with external components cx cx 16mhz xtal1 xtal2 evdd c trim c trim c par c par at86rf230 pcb xtal_trim[3:0] xtal_trim[3:0] 9.6.3 external reference frequency setup when using an external reference frequency, the signal needs to be connected to pin xtal1 as indicated in figure 9-5 and the register xtal_mode of register 0x12 (xosc_ct rl) need to be set to the external oscillator mode. the oscillation peak-to- peak amplitude shall be 400 mv, but not larger than 500 mv. figure 9-5. setup for using an external frequency reference xtal1 xtal2 at86rf230 pcb 16 mhz 9.6.4 master clock signal output (clkm) the generated reference clock signal can be fed to a microcontroller using pin 17 (clkm). the internal 16 mhz raw clock can be divided by an internal prescaler. thus, clock frequencies of 16 mhz, 8 mhz, 4 mhz, 2 mhz or 1 mhz can be supplied by pin clkm. the clkm frequency and pin driver strength is configurable using register 0x03 (trx_ctrl_0). there are two possibilities to change the clkm frequency. if clkm_sha_sel = 0, changing the register bits clkm_ctrl (register 0x03, trx_ctrl_0) immediately affects the clkm clock rate. otherwise (clkm_sha_sel = 1) the new clock rate is supplied when leaving the sleep state the next time.
69 5131e-mcu wireless-02/09 at86rf230 to reduce power consumption and spurious emissions, it is recommended to turn off the clkm clock when not in use or to reduce its driver strength to a minimum, refer to section 4.3. note: during reset procedure, see section 7.1.4.2, register bits clkm_ctrl are shadowed. although th e clock setting of clkm remains after reset, a read access to register bits clkm_ctrl delivers the reset value 1. for that reason it is recommended to write the previous configuration (before reset) to t he clkm_ctrl to align the radio transceiver behavior and register configuration. otherwise the clkm clock rate is set back to the reset value (1 mhz) after the next sleep cycle. for example if the clkm clock rate is configured to 16 mhz the clkm rate remains at 16 mhz after a reset, however the register bits clkm_ctrl are set back to 1. since clkm_sha_sel reset value is 1, the clkm clock rate would change to 1 mhz after the next sleep cycle if the clkm_ctrl setting is not updated. 9.6.5 register description regis ter 0x03 (trx_ctrl_0) the trx_ctrl_0 register controls the driv e current of the digital output pads and the clkm clock rate. bit 7 6 5 4 0x03 pad_io pad_io_clkm trx_ctrl_0 read/write r/w r/w r/w r/w reset value 0 0 0 1 bit 3 2 1 0 0x03 clkm_sha_sel clkm_ctrl trx_ctrl_0 read/write r/w r/w r/w r/w reset value 1 0 0 1 ? bit [7:6] ? pad_io refer to in section 4.3.3. ? bit [5:6] ? pad_io_clkm the register bits pad_io_clkm set the output driver current of pin clkm. table 9-9. clkm driver strength register bit value description 0 2 ma 1 4 ma 2 6 ma pad_io_clkm 3 8 ma ? bit 3 ? clkm_sha_sel the register bit clkm_sha_sel defines t he commencement of the clkm clock rate modifications when changing register bits clkm_ctrl. table 9-10. commencement of clkm clock rate modification register bit value description clkm_sha_sel 0 clkm clock rate changes immediately
70 5131e-mcu wireless-02/09 at86rf230 register bit value description 1 clkm clock rate changes after sleep cycle ? bit [2:0] ? clkm_ctrl the register bits clkm_ctrl set clock rate of pin clkm. table 9-11. clock rate at pin clkm register bit value description 0 no clock, pin set to logic low 1 1 mhz 2 2 mhz 3 4 mhz 4 8 mhz 5 16 mhz 6 reserved clkm_ctrl 7 reserved register 0x12 (xosc_ctrl) the register xosc_ctrl controls the operation of the crystal oscillator. bit 7 6 5 4 0x12 xtal_mode xosc_ctrl read/write r/w r/w r/w r/w initial value 1 1 1 1 bit 3 2 1 0 0x12 xtal_trim xosc_ctrl read/write r/w r/w r/w r/w initial value 0 0 0 0 ? bit [7:4] ? xtal_mode the register bit xtal_mode sets the operating mode of the crystal oscillator. table 9-12. crystal oscillator operating mode register bit value description 0x0 crystal oscillator disabled, no clock signal is fed to the internal circuitry. 0x4 internal crystal oscillator disabled, use external reference frequency xtal_mode 0xf internal crystal oscillator enabled ? bit [3:0] ? xtal_trim the register bits xtal_trim control two internal capacitance arrays connected to pins xtal1 and xtal2. a capacitance value in the range from 0 pf to 4.5 pf is selectable with a resolution of 0.3 pf. table 9-13. crystal oscillator trimming capacitors register bit value description xtal_trim 0x0 0.0 pf, trimming capacitors disconnected
71 5131e-mcu wireless-02/09 at86rf230 register bit value description 0x1 0.3 pf, trimming capacitor switched on ? 0xf 4.5 pf, trimming capacitor switched on 9.7 frequency synthesizer (pll) the main pll features are: ? generate rx/tx frequencies for all ieee 802.15.4 - 2.4 ghz channels ? fully integrated fractional-n synthesizer ? autonomous calibration loops for stable operation within the operating range ? two pll-interrupts for status indication 9.7.1 overview the synthesizer of the at86rf230 is implem ented as a fractional-n pll. the pll is fully integrated and configurable by regi sters 0x08 (phy_cc_cc a), 0x1a (pll_cf) and 0x1b (pll_dcu). the pll is turned on when entering the state pll_on and stays on in all receive and transmit states. the pll settles to the corr ect frequency needed for rx or tx operation according to the adjusted channel center frequency in register 0x08 (phy_cc_cca). two calibration loops ensure correct pll functionality within the specified operating limits. 9.7.2 rf channel selection the pll is designed to support 16 channel s in the ieee 802.15.4 ? 2.4 ghz band with a channel spacing of 5 mhz. the center frequency f ch of these channels is defined as follows: f ch = 2405 + 5 (k ? 11) [mhz], for k = 11, 12, ..., 26 where k is the channel number. the channel k is selected by register bi ts channel (register 0x08, phy_cc_ca). 9.7.3 calibration loops the center frequency control loop ensures a correct center frequency of the vco for the currently programmed channel. the delay calibration unit compensates the phase errors inherent in fractional-n plls. using this technique, unwanted spurious frequency components beside the rf carrier are suppressed, and the pll behaves similar to an integer-n pll. both calibration routines are initiated automatically when the pll is turned on. additionally, the center frequen cy calibration is running when the pll is programmed to a different channel (register bits channel in register 0x08). if the pll operates for a long time on the same channel or the operating temperature changes significantly, the control loops s hould be initiated manually. the recommended calibration interval is 5 min. both calibration loops can be initiated manually by setting pll_cf_start = 1 of register 0x1a (pll_cf) and register bi t pll_dcu_start = 1 of register 0x1b
72 5131e-mcu wireless-02/09 at86rf230 (pll_dcu). to start the calibrations routin es the device should be in state pll_on. the center frequency tuning takes a maximum of 80 s. the completion is indicated by a pll_lock interrupt. the delay cell calibration loop is completed after 6 s. this is typically not indicated by a pll_lock interrupt. 9.7.4 pll interrupt handling there are two different interrupts indicating the pll status (see register 0x0f). the pll_lock interrupt indicates that the p ll has locked. the pll_unlock interrupt indicates an unexpected unlock condition. a pll_lock interrupt clears any preceding pll_unlock interrupt automatically and vice versa. a pll_lock interrupt occurs in the following situations: ? state change from trx_off to pll_on/rx_on ? channel change in states pll_on/rx_on ? initiating a center frequency tuning manually the state transition from busy_tx to pll_o n can also initiate a pll_lock interrupt, due to the pll settling back to the rx frequency. any other occurrences of pll interrupts indicate erroneous behavior and require checking of the actual device status. 9.7.5 register description regis ter 0x08 (phy_cc_cca) the phy_cc_cca register contains register bits to initiate and control the cca measurement as well as to set the channel center frequency. bit 7 6 5 4 0x08 cca_request cca_mode channel phy_cc_cca read/write r/w r/w r/w r/w reset value 0 0 1 0 bit 3 2 1 0 0x08 channel phy_cc_cca read/write r/w r/w r/w r/w reset value 1 0 1 1 ? bit 7 ? cca_request refer to section 8.6.4. ? bit [6:5] ? cca_mode refer to section 8.6.4. ? bit [4:0] ? channel the register bits channel define the rx /tx channel. the channel assignment is according to ieee 802.15.4. table 9-14. channel assignment for ieee 802.15.4 ? 2.4 ghz band register bit value channel number center frequency [mhz] 0x0b 11 2405 0x0c 12 2410 0x0d 13 2415 channel 0x0e 14 2420
73 5131e-mcu wireless-02/09 at86rf230 register bit value channel number center frequency [mhz] 0x0f 15 2425 0x10 16 2430 0x11 17 2435 0x12 18 2440 0x13 19 2445 0x14 20 2450 0x15 21 2455 0x16 22 2460 0x17 23 2465 0x18 24 2470 0x19 25 2475 0x1a 26 2480 register 0x1a (pll_cf) the register pll_cf controls the operation of the center frequency calibration loop. bit 7 6 5 4 0x1a pll_cf_start reserved pll_cf read/write r/w r/w r/w r/w reset value 0 1 0 1 bit 3 2 1 0 0x1a reserved pll_cf read/write r/w r/w r/w r/w reset value 0 1 1 1 ? bit 7 ? pll_cf_start pll_cf_start = 1 initiates the center frequen cy calibration. the calibration cycle has finished after a maximum of 80 s. the register bit is cleared immediately after the register write operation. ? bit [6:0] ? reserved register 0x1b (pll_dcu) the register pll_dcu controls the operation of the delay cell calibration loop. bit 7 6 5 4 0x1b pll_dcu_start reserved pll_dcu read/write r/w r r/w r/w reset value 0 0 1 0 bit 3 2 1 0 0x1b reserved pll_dcu read/write r/w r/w r/w r/w reset value 0 0 0 0
74 5131e-mcu wireless-02/09 at86rf230 ? bit 7 ? pll_dcu_start pll_dcu_start = 1 initiates the delay cell calibration. the calibration cycle has finished after maximum of 6 s. the register bit is cleared immediately after the register write operation. ? bit [6:0] ? reserved 9.8 automatic filter tuning (ftn) the filter-tuning unit is a separate block within the at86rf230. the filter-tuning result is used to provide a correct ssbf transfer function and pll loop-filter time constant independent of temperature effects and part-to-part variations. a calibration cycle is initiated automatically when entering the trx_off state from the sleep, reset or p_on states.
75 5131e-mcu wireless-02/09 at86rf230 10 radio transceiver usage this section describes basic procedures to receive and transmit frames using the at86rf230. for a detailed programming description refer to application note avr2009 ?at86rf230 ? software programming model?. 10.1 frame receive procedure while in state rx_on the radio transceiver searches for incoming frames on the selected channel. a detection of a valid ieee 802.15.4 frame is indicated by an irq_2 (rx_start) interrupt. the frame reception is completed when issuing the irq_3 (trx_end) interrupt. waiting for irq_3 (trx_end) interrupt before uploading the frame to the microcontroller is recommended for operations considered to be non time critical. figure 9-6 illustrates the fr am e receive procedure. figure 9-6. frame receive procedure - transactions between at86rf230 and microcontroller at86rf230 microcontroller critical protocol timing could require starti ng the frame upload as soon as possible. the first byte of the frame data can be read 32 s after the irq_2 (rx_start) interrupt. the microcontroller must ensure to read slower than the frame is received. otherwise, the frame buffer wills under run, irq_6 (trx _ur) interrupt is issued. the frame data are not valid anymore and need to read again. the lqi byte can be uploaded to the microcontroller after the irq_3 (trx_end) interrupt was issued. 10.2 frame transmit procedure a frame transmission comprises two actions, a frame download to the frame buffer and the transmission of the frame buffer content. both actions can be run in parallel if required by critical protocol timing. figure 9-7 illustrates the frame transmit procedure, when downloading and transmitting the frame co nsecutively. after a frame dow nload by a frame buffer write access, the frame transmission is initiated by asserting pin slp_tr or writing the trx command tx_start to register 0x02 (trx_state), while the radio transceiver is in state pll_on. the completion of the transmissi on is indicated by an irq_3 (trx_end) interrupt.
76 5131e-mcu wireless-02/09 at86rf230 figure 9-7. frame transmit procedure - transactions between at86rf230 and microcontroller alternatively, the frame transmission can be started before the frame data download as described in figure 9-8. this is useful for time critica l applications. at the rising edge of spl_tr, the radio transceiver starts transmitting the preamble and the sfd field, which takes about 176 s (see figure 7-2). the first byte of the psdu must be available in the frame buffer before this time. the spi data rate must be higher than 250 kbit/s to ensure that no frame buffer under run occurs (irq_6, trx_ur). figure 9-8. time optimized frame transmit procedure - transactions between at86rf230 and microcontroller
77 5131e-mcu wireless-02/09 at86rf230 11 technical parameters 11.1 absolute maximum ratings note: stresses beyond those listed under ?absolute maximum ratings? may cause permanent damage to the device. this is a st ress rating only and functional operation of the device at these or any other conditions beyond those indicated in the operational sections of this specification are not im plied. exposure to absolute maximum rating conditions for extended periods may affect device reliability. table 11-1. absolute maximum ratings no parameter symbol min typ max unit conditions/notes 11.1.1 storage temperature t stor -50 150 c 11.1.2 lead temperature t lead 260 c 11.1.3 esd robustness v esd 4 750 kv v compl. to [2] compl. to [3] 11.1.4 input rf level p rf +14 dbm 11.1.5 voltage on all pins (except pins 4, 5, 13, 14, 29) -0.3 v dd +0.3 11.1.6 voltage on pins 4, 5, 13, 14, 29 -0.3 2.0 11.2 recommended operating range table 11-2. operating range no parameter symbol min typ max unit conditions/notes 11.2.1 operating temperature range t op -40 +85 c 11.2.2 supply voltage v dd 1.8 3.0 3.6 v 11.2.3 supply voltage (on pins 13, 14, 29) v dd1.8 1.65 1.8 1.95 v when using external voltage regulators (see section 9.4). 11.3 digital pin specifications test conditions (unless otherwise stated): t op = 25c table 11-3. digital pin specifications no parameter symbol min typ max unit conditions/notes 11.3.1 high level input voltage v ih v dd ? 0.4 v 11.3.2 low level input voltage v il 0.4 v 11.3.3 high level output voltage v oh v dd ? 0.4 v for all output driver strengths defined in trx_ctrl_0 11.3.4 low level output voltage v ol 0.4 v for all output driver strengths defined in trx_ctrl_0
78 5131e-mcu wireless-02/09 at86rf230 11.4 digital interface ti ming specifications test conditions (unless otherwise stated): v dd = 3v, t op = 25c table 11-4. digital interface timing parameters no parameter symbol min typ max unit conditions/notes 11.4.1 sclk frequency (synchronous mode) 8 mhz 11.4.2 sclk frequency (asynchronous mode) 7.5 mhz 11.4.3 sel low to miso active t 1 180 ns 11.4.4 sclk to miso out t 2 10 ns data hold time 11.4.5 mosi setup time t 3 10 ns 11.4.6 mosi hold time t 4 10 ns 11.4.7 lsb last byte to msb next byte t 5 250 ns 11.4.8 sel high to miso tristate t 6 10 ns 11.4.9 slp_tr pulse width t 7 65 ns tx start trigger 11.4.10 spi idle time t 8 250 ns idle time between consecutive spi accesses 11.4.11 last sclk to sel high t 9 250 ns 11.4.12 reset pulse width 625 ns 10 clock cycles at 16 mhz 11.4.13 output clock frequency (clkm) 0 1 2 4 8 16 mhz mhz mhz mhz mhz mhz programmable in register trx_ctrl_0 11.5 general rf specifications test conditions (unless otherwise stated): v dd = 3v, f = 2.45 ghz, t op = 25c, measurement setup see figure 5-1 table 11-5. general rf parameters no parameter symbol min typ max unit conditions/notes 11.5.1 frequency range f 2405 2480 mhz as specified in [1] 11.5.2 bit rate f bit 250 kbit/s as specified in [1] 11.5.3 chip rate f chip 2000 kchip/s as specified in [1] 11.5.4 reference oscillator frequency f clk 16 mhz 11.5.5 reference oscillator settling time 0.5 1 ms leaving sleep state to clock available at pin clkm 11.5.6 reference frequency accuracy for proper functionality -60 +60 ppm 40 ppm is required by [1] 11.5.7 tx signal 20 db bandwidth b 20db 2.8 mhz rbw 100 khz vbw 300 khz
79 5131e-mcu wireless-02/09 at86rf230 11.6 transmitter specifications test conditions (unless otherwise stated): v dd = 3v, f = 2.45 ghz, t op = 25c, measurement setup see figure 5-1 table 11-6. tx parameters no parameter symbol min typ max unit conditions/notes 11.6.1 output power p tx 0 3 6 dbm maximum configurable value 11.6.2 output power range 20 db configurable in register phy_tx_pwr 11.6.3 output power tolerance 3 db 11.6.4 tx return loss 10 db 11.6.5 evm 8 %rms 11.6.6 harmonics 2nd harmonic 3rd harmonic -38 -45 dbm dbm 11.6.7 spurious emissions 30 ? 1000 mhz >1 ? 12.75 ghz 1.8 ? 1.9 ghz 5.15 ? 5.3 ghz -36 -30 -47 -47 dbm dbm dbm dbm complies with en 300 328/440, fcc-cfr-47 part 15, arib std-66, rss-210 11.7 receiver specifications test conditions (unless otherwise stated): v dd = 3v, f = 2.45 ghz, t op = 25c, measurement setup see figure 5-1 table 11-7. rx parameters no parameter symbol min typ max unit conditions/notes 11.7.1 receiver sensitivity -101 dbm awgn channel, per 1%, psdu length of 20 octets 11.7.2 rx return loss 10 db 100 ? differential impedance 11.7.3 noise figure nf 6 db 11.7.4 maximum rx input level 10 dbm per 1%, psdu length of 20 octets 11.7.5 adjacent channel rejection -5 mhz 34 dbm per 1%, psdu length of 20 octets, p rf = -82 dbm 11.7.6 adjacent channel rejection +5 mhz 36 dbm per 1%, psdu length of 20 octets, p rf = -82 dbm 11.7.7 alternate adjacent channel rejection -10 mhz 52 dbm per 1%, psdu length of 20 octets, p rf = -82 dbm 11.7.8 alternate adjacent channel rejection +10 mhz 53 dbm per 1%, psdu length of 20 octets, p rf = -82 dbm 11.7.9 spurious emissions lo leakage 30 ? 1000 mhz >1 ? 12.75 ghz -75 -57 -47 dbm dbm dbm
80 5131e-mcu wireless-02/09 at86rf230 no parameter symbol min typ max unit conditions/notes 11.7.10 tx/rx carrier frequency offset tolerance -300 300 khz sensitivity loss < 2 db; equals 120 ppm ([1] requires 80 ppm) 11.7.11 3rd-order intercept point iip3 -9 db at maximum gain offset freq. interf. 1 = 5 mhz offset freq. interf. 2 = 10 mhz 11.7.12 2nd-order intercept point iip2 24 db at maximum gain offset freq. interf. 1 = 60 mhz offset freq. interf. 2 = 62 mhz 11.7.13 rssi tolerance 5 db 11.7.14 rssi dynamic range 81 db 11.7.15 rssi resolution 3 db 11.7.16 rssi sensitivit y -91 dbm defined as rssi_base_val 11.7.17 minimum rssi value 0 p rf < rssi_base_val 11.7.18 maximum rssi value 28 p rf rssi_base_val + 81 db 11.8 current consumption specifications test conditions (unless otherwise stated): v dd = 3v, f = 2.45 ghz, t op = 25c, measurement setup see figure 5-1 table 11-8. current consumption no parameter symbol min typ max unit conditions/notes 11.8.1 supply current transmit state i busy_tx 16.5 14.5 12.5 9.5 ma ma ma ma p tx = 3 dbm p tx = 1 dbm p tx = -3 dbm p tx = -17 dbm (at each output power level, the supply current consumption can be decreased by approx. 2 ma if reducing v dd to 1.8v.) 11.8.2 supply current receive state i rx_on 15.5 ma state: rx_on 11.8.3 supply current trx_off state i trx_off 1.5 ma state: trx_off 11.8.4 supply curr ent sleep state i sleep 0.02 a state: sleep 11.8.5 supply current pll_on state i pll_on 7.8 ma state: pll_on 11.9 crystal parameter requirements table 11-9. crystal parameter requirements no parameter symbol min typ max unit conditions/notes 11.9.1 crystal frequency f 0 16 mhz 11.9.2 load capacitance c l 8 14 pf 11.9.3 static capacitance c 0 7 pf 11.9.4 series resistance r 1 100 ?
81 5131e-mcu wireless-02/09 at86rf230 12 register reference the at86rf230 provides a register space of 64 8-bit registers, which is used to configure, control and monitor the radio transceiver. the registers can be accessed in any order. note: all registers not mentioned within the foll owing table are reserved for internal use and must not be overwritten. when writing to a register, any reserved bits shall be overwritten only with their reset value (see table 12-2). table 12-1. register summary ? non reserved registers addr. name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 page 0x01 trx_status cca_done cca_status reserved trx_status pg. 27, 38, 55 0x02 trx_state trac_status trx_cmd pg. 28, 39 0x03 trx_ctrl_0 pad_io pad_io_clkm clkm_sha_sel clkm_ctrl pg. 7, 69 0x05 phy_tx_pwr tx_auto_crc_on reserved tx_pwr pg. 49, 59 0x06 phy_rssi rx_crc_valid reserved rssi pg. 50, 52 0x07 phy_ed_level ed_level pg. 51 0x08 phy_cc_cca cca_request cca_mode channel pg. 56, 72 0x09 cca_thres reserved cca_ed_thres pg. 57 0x0e irq_mask mask_bat_low mask_trx_ur reserved mask_trx_end mask_rx_start mask_pll_unlock mask_pll_lock pg. 20 0x0f irq_status bat_low trx_ur reserved trx_end rx_start pll_unlock pll_lock pg. 20 0x10 vreg_ctrl avreg_ext avdd_ok reserved dvreg_ext dvdd_ok reserved pg. 63 0x11 batmon reserved batmon_ok batmon_hr batmon_vth pg. 65 0x12 xosc_ctrl xtal_mode xtal_trim pg. 70 0x1a pll_cf pll_cf_start reserved pg. 73 0x1b pll_dcu pll_dcu_start reserved pg. 73 0x1c part_num part_num pg. 16 0x1d version_num version_num pg. 16 0x1e man_id_0 man_id_0 pg. 17 0x1f man_id_1 man_id_1 pg. 17 0x20 short_addr_0 short_addr_0 pg. 42 0x21 short_addr_1 short_addr_1 pg. 42 0x22 pan_id_0 pan_id_0 pg. 42 0x23 pan_id_1 pan_id_1 pg. 42 0x24 ieee_addr_0 ieee_addr_0 pg. 43 0x25 ieee_addr_1 ieee_addr_1 pg. 43 0x26 ieee_addr_2 ieee_addr_2 pg. 43 0x27 ieee_addr_3 ieee_addr_3 pg. 43 0x28 ieee_addr_4 ieee_addr_4 pg. 43 0x29 ieee_addr_5 ieee_addr_5 pg. 43 0x2a ieee_addr_6 ieee_addr_6 pg. 44 0x2b ieee_addr_7 ieee_addr_7 pg. 44 0x2c xah_ctrl max_frame_retries max_csma_retries reserved pg. 40 0x2d csma_seed_0 csma_seed_0 pg. 41 0x2e csma_seed_1 min_be aack_set_pd reserved i_am_coord csma_seed_1 pg. 41
82 5131e-mcu wireless-02/09 at86rf230 notes: ? reset values in table 12-2 are only valid after a power on reset. after a reset pro cedure ( rst = l) as described in section 7.1.4.2 the reset values of selected regi sters (e.g. registers 0x01, 0x10, 0x11) can differ from that in table 12-2. ? read value of register 0x30 after a reset in state: p_on 0x11 any other state 0x07 table 12-2. register summary ? reset values address reset value address reset value address reset value address reset value 0x00 0x00 0x10 0x00 0x20 0x00 0x30 0x00 0x01 0x00 0x11 0x02 0x21 0x00 0x31 0x00 0x02 0x00 0x12 0xf0 0x22 0x00 032 0x00 0x03 0x19 0x13 0x00 0x23 0x00 0x33 0x00 0x04 0x00 0x14 0x00 0x24 0x00 0x34 0x00 0x05 0x00 0x15 0x00 0x25 0x00 0x35 0x00 0x06 0x00 0x16 0x00 0x26 0x00 0x36 0x00 0x07 0x00 0x17 0x00 0x27 0x00 0x37 0x00 0x08 0x2b 0x18 0x58 0x28 0x00 0x38 0x00 0x09 0xc7 0x19 0x55 0x29 0x00 0x39 0x40 0x0a 0xbc 0x1a 0x5f 0x2a 0x00 0x3a 0x00 0x0b 0xa7 0x1b 0x20 0x2b 0x00 0x3b 0x00 0x0c 0x04 0x1c 0x02 0x2c 0x38 0x3c 0x00 0x0d 0x00 0x1d 0x02 0x2d 0xea 0x3d 0x00 0x0e 0xff 0x1e 0x1f 0x2e 0xc2 0x3e 0x00 0x0f 0x00 0x1f 0x00 0x2f 0x00 0x3f 0x00
83 5131e-mcu wireless-02/09 at86rf230 abbreviations aack ? auto acknowledge ack ? acknowledge adc ? analog-to-digital converter agc ? automatic gain control aret ? auto retry avreg ? analog voltage regulator awgn ? additive white gaussian noise batmon ? battery monitor bbp ? base-band processor bg ? band gap reference bom ? bill of material cca ? clear channel assessment crc ? cyclic redundancy check csma ? carrier sense multiple access cw ? continuous wave dclk ? digital clock dcu ? delay calibration unit dvreg ? digital voltage regulator ed ? energy detection esd ? electro static discharge evm ? error vector magnitude fcs ? frame check sequence fcf ? frame control field fifo ? first in first out ftn ? automatic filter tuning gpio ? general purpose input output ism ? industrial, scientific, and medical ldo ? low-drop output lna ? low-noise amplifier lo ? local oscillator lqi ? link-quality indication lsb ? least significant bit mac ? medium access control mfr ? mac footer mhr ? mac header msb ? most significant bit msdu ? mac service data unit msk ? minimum shift keying nop ? no operation o-qpsk ? offset-quadrature phase shift keying pa ? power amplifier
84 5131e-mcu wireless-02/09 at86rf230 pan ? personal area network pcb ? printed circuit board per ? packet error rate phy ? physical layer phr ? phy header pll ? phase-locked loop por ? power-on reset ppf ? poly-phase filter prbs ? pseudo random binary sequence psdu ? phy service data unit qfn ? quad flat no-lead package ram ? random access memory rbw ? resolution band width rssi ? received signal strength indicator rx ? receiver sfd ? start-of-frame delimiter shr ? synchronization header spi ? serial peripheral interface sram ? static random access memory ssbf ? single side band filter tx ? transmitter vbw ? video band width vco ? voltage controlled oscillator vreg ? voltage regulator xosc ? crystal stabilized oscillator
85 5131e-mcu wireless-02/09 at86rf230 13 ordering information ordering code package voltage range temperature range AT86RF230-ZU qn 1.8v ? 3.6v industrial (-40 c to +85 c) lead-free/halogen-free package type description qn 32qn1, 32-lead 5.0x5.0 mm body, 0.50 mm pitch, quad flat no-lead package (qfn) sawn note: t&r quantity 4,000. please contact your local atmel sales office for more detailed ordering information and minimum quantities. 14 soldering information recommended soldering profile is spec ified in ipc/jedec j-std-.020c. 15 package thermal properties thermal resistance velocity [m/s] theta ja [k/w] 0 40.9 1 35.7 2.5 32.0
86 5131e-mcu wireless-02/09 at86rf230 16 package drawing ? 32qn1 title drawing no. gpc rev. package drawing contact: packagedrawings@atmel.com 32qn2 zjz a 32qn2 , 32-lead 5.0 x 5.0 mm body, 0.50 mm pitch, quad flat no lead package (qfn) sawn 11/26/07 notes: 1. this drawing is for general information only. refer to jedec drawing mo-220, variation vhhd-6, for proper dimensions, tolerances, datums, etc. 2. dimension b applies to metallized terminal and is measured between 0.15 mm and 0.30 mm from the terminal tip. if the terminal has the optional radius on the other end of the terminal, the dimension should not be measured in that radius area. common dimensions (unit of measure = mm) symbol min nom max note d 5.00 bsc e 5.00 bsc d2 3.20 3.30 3.40 e2 3.20 3.30 3.40 a 0.80 0.90 1.00 a1 0.0 0.02 0.05 a2 0.0 0.65 1.00 a3 0.20 ref l 0.30 0.40 0.50 e 0.50 bsc b 0.18 0.23 0.30 2 pin 1 corner pin 1 corner pin 1 corner pin 1 corner side view side view bottom view bottom view top view top view a3 a3 l b e2 e2 d2 d2 e e d a a1 a1 a2 a2
87 5131e-mcu wireless-02/09 at86rf230 appendix a - continuous transmission test mode the continuous transmission test mode offers the following features: ? continuous frame transmission ? continuous wave signal transmission a.1 - overview the at86rf230 offers a continuous transmission test mode to support final application/production tests as well as certific ation tests. using this test mode the radio transceiver transmits continuously a prev iously downloaded frame data (prbs mode) or a continuous wave signal (cw mode). in cw mode three different signal frequencies can be transmitted: f 1 = f ch ? 2 mhz f 2 = f ch + 0.5 mhz f 3 = f ch - 0.5 mhz where f ch is the center frequency of the curren t programmed cannel in register 0x08 (phy_cc_cca). note that it is not possible to transmit a cw signal on the channel center frequency. before starting a cw signal transmission valid data needs to be downloaded to the frame buffer (refer to section 6.2.2), e.g a phr field denotes a frame len gth of 1 and one octet psdu data. in prbs mode the transmission center frequency is f ch . data downloaded to the frame buffer must contain at least a valid frame length field (see sections 8.1 and 9.1). it is recomme nded to use a frame of maximum length (127 bytes) and arbitrary psdu data. in contrast to normal frame transmi ssion here the shr and the phr are not transmitted. the transmission starts with the psdu data and is repeated continuously. a.2 - configuration before enabling the continuous transmission test mode (tst = 1) all register configurations shall be done as follows: ? radio transceiver initialization (trx_status = trx_off) ? tx channel selection (optional) ? tx output power setting (optional) ? frame data download (random sequence of max. length) ? mode selection (prbs/cw) setting tst = 1 enables the continuous transm ission test mode. the test system or a microcontroller has to overwrite the pull down resistor r1 connected to the tst pin (see figure 5-1). the pull down resistor ensures a disabled test functionality during normal operation (ts t = 0). the transmission is started after enabling the pll (trx_cmd = pll_on) and writing the tx_start command to register 0x02. the detailed programming sequence is shown in figure a-1.
88 5131e-mcu wireless-02/09 at86rf230 figure a-1. programming sequence - continuous transmission configure continuous tx (2) reset write 0x10 to register 0x03 write 0x33 to register 0x08 write 0x00 to register 0x05 write f_word to register 0x3d write 0x01 to register 0x0e write 0x0f to register 0x36 set pin tst = h write 0x03 to register 0x02 write 0x09 to register 0x02 write 0x02 to register 0x02 set pin tst = l signal measurement (use rfp|rfn) read register 0x01 reset 0x08 1 2 3 4 5 6 12 13 14 15 17 frame download set irq_mask register (enable pll_lock) set trx_state register (state = force_trx_off) set clkm set channel (f ch ) set tx output power (maximum tx output power) modulated (f ch ): f_word = 0x00 cw (f ch - 2.0mhz): f_word = 0x10 cw (f ch - 0.5mhz): f_word = 0x80 cw (f ch + 0.5mhz): f_word = 0xc0 configure continuous tx (1) 9 enable continuous tx test mode (tst = h) 11 set trx_state register (state = pll_on) interrupt: pll_lock (irq1) set trx_state register (state = tx_start) reset tst for normal operation (tst = l) 16 load tx frame to frame buffer 8 10 7 verify trx_off state read register 0x0f 0x01 required setting optional setting legend: tst pin setting special settings for continuous tx a.3 - disclaimer the functionality of the continuous transmi t mode is not characterized by atmel and therefore not guaranteed. the normal operation of the at86rf230 is only guaranteed if pin tst is always logic low.
89 5131e-mcu wireless-02/09 at86rf230 appendix b - errata at86rf230 rev. b no known errata. at86rf230 rev. a 1. data frames with destination address=0xffff is acknowledged in rx_aack according to ieee 802.15.4-2003 data fr ames with destination address=0xffff (broadcast) should not have the acknowledg ment request subfield set in the frame control field. if such a non-standard co mpliant data frame arrives, a device in rx_aack state acknowledges that frame. fix/workaround use only standard compliant frames, i.e. do not initiate frames with destination address=0xffff (broadcast) and the acknowledgment request subfield set. 2. frame upload in rx_aack the following frames are not uploaded: (1) data frames and command frames with destination pan id=0xffff and extended destination addressing mode (2) beacon frames, when the pan id of the receiving node is set to 0xffff. fix/workaround (1) use basic operating mode for orphan scanning (2) use basic operating mode for network scanning 3. tx_aret returns trac_status= success even though transaction failed it might happen that under very special condit ions (e.g. noisy network environment) the status bit trac_status (register 0x 02) after transmission of a frame is success even though the transaction failed. example a node transmits a frame with the acknowledgment request subfield set to logic high and waits for an incoming ack. if no frame is received at the end of the ack wait period (54 symbols), but a valid preamble is detected (e.g. jammer/interferer signal), the tx_aret procedure is finished immedi ately. a trx_end interrupt is generated. the trac_status is not updated and t hus shows the default value success. fix/workaround the workaround comprises two changes: 1. set register bits max_frame_retries to 0. this prevents any retransmissions in the tx_aret procedure. the frame retransmission has to be implemented in s/w. a retransmission does not require a frame download again, only tx_start command is necessary. 2. control of the tx_aret proce dure should follow these steps: o trx_status == tx_aret_on o set trx_cmd = tx_start and download frame o poll for trx_status == busy_tx_aret
90 5131e-mcu wireless-02/09 at86rf230 o set trx_cmd = rx_on o wait for trx_end irq o read trac_status o set trx_cmd = tx_aret_on o poll for trx_status == tx_aret_on switching to rx_on is not executed during busy_tx_aret but immediately after busy_tx_aret has completed. this enables the receiver to receive a frame which arrives shortly before the end of the ack wait period. in this case trac_status is not accidentally set to success and is still correct (no_ ack), as long as the frame is received. that means the software has additional time to read the trac_status. using the workaround mentioned above, t he failure occurrence is considerably reduced. a wrong trac_status can still be observed, but very seldom (one of million transmissions). 4. sensitivity to continuous wave interferers due to the high receiver sensitivity continuous wave interferers may cause rx_start interrupts. this may result in missed frames since the receiver is kept busy detecting preambles and sfd. one cause of continuous wave interferers may be due to crosstalk from clock. fix/workaround for further details see application note avr2005 "design considerations for the at86rf230". 5. trx_end_irq occurs sometimes too late in tx_aret_on state this behavior can be observed, if t he procedure tx_aret performs frame retransmissions. fix/workaround set register bit max_frame_retries = 0 (register 0x2c) and implement frame retries by software. a frame retransmission does not require downloading the frame again, only tx_start command is necessary. 6. tx_aret ack wait time too short the maximum number of symbols waiting for an acknowledgment frame should be 54 symbols as defined in ieee 802.15.4-2003. the implemented waiting time is 46 symbols. fix/workaround none 7. cca request is not executed a requested cca may be rejected without execution. in this case the cca_done bit indicates ?cca calculation in progress? ev en though the calculation must be finished already. fix/workaround the trx_status is rx_on. to initiate a cca request, switch to pll_on state and back to rx_on state. immediately afte r the state change initiate a cca request. it is not necessary to confirm the state changes.
91 5131e-mcu wireless-02/09 at86rf230 references [1] ieee std 802.15.4-2003: wireless medi um access control (mac) and physical layer (phy) specifications for low-rate wireless personal area networks (lr-wpans) [2] ansi / esd-stm5.1-2001: esd association standard test method for electrostatic discharge sensitivity testing ? human body model (hbm) [3] esd-stm5.3.1-1999: esd association standard test method for electrostatic discharge sensitivity testing ? charged device model (cdm)
92 5131e-mcu wireless-02/09 at86rf230 data sheet revision history rev. 5131e-zigb-02/04/09 1. removed preliminary statement 2. updated parameter 11.4.4 3. minor editorial changes rev. 5131d-zigb-12/03/07 the at86rf230 data sheet was fully revised and modifications of silicon revision at86rf230 rev. b were incorporated. a migration note of silicon revision a to revision b is available on www.atmel.com . the mo st important modifications are: 4. device version number in register 0x 1d (version_num) changed to 2 (section 6.3) 5. spi interface: miso pin is updated on falling edge at pin sclk (section 6.1) 6. extended operating mode state diagr am: state changes towards rx_aack_on and tx_aret_on ( figure 7-5) 7. enhanced return code of tx_aret transa ction in register bits trac_status of register 0x02 (section 7.2.3.2) 8. fcs check of received frames in basic operating mode (section 8.2) 9. support of pending data indication in extended operating mode (sections 7.2.3.1, 7.2.3.2) 10. update package drawing (section 16) rev. 5131c-zigb-05/22/07 1. major revise of sections 1 to 10 2. added ?appendix a - continuous transmission test mode? 3. added ?appendix b - errata? rev. 5131a-zigb-06/14/06 1. initial release
93 5131e-mcu wireless-02/09 at86rf230 table of contents 1 pin-out diagram .................................................................................. 2 disclaimer............................................................................................... 2 2 overview .............................................................................................. 2 3 general circui t description ................................................................ 3 4 pin desc ription .................................................................................... 4 4.1 supply and ground pins ........................................................................................ 4 4.2 analog and rf pins ............................................................................................... 5 4.3 digita l pins.............................................................................................................. 6 4.3.1 driver strengt h settings of digi tal output pins.............................................................. 6 4.3.2 pull-up and pull-d own configuration of digital i nput pi ns.............................................. 7 4.3.3 register description ..................................................................................................... . 7 5 applicati on circuit .............................................................................. 8 6 microcontro ller int erface .................................................................. 10 6.1 spi timing description......................................................................................... 11 6.2 spi pr otocol.......................................................................................................... 12 6.2.1 register access mode................................................................................................. 12 6.2.2 frame buffe r access modes ....................................................................................... 13 6.2.3 sram access mode.................................................................................................... 14 6.3 radio transceive r identification ........................................................................... 16 6.3.1 register description .................................................................................................... 16 6.4 sleep/wake-up and trans mit signal (slp_tr)................................................... 17 6.5 interru pt logi c....................................................................................................... 19 6.5.1 overview ................................................................................................................. .... 19 6.5.2 register description .................................................................................................... 20 7 operatin g m odes............................................................................... 21 7.1 basic oper ating mode.......................................................................................... 21 7.1.1 state control ............................................................................................................ ... 21 7.1.2 basic operatin g mode description .............................................................................. 22 7.1.3 interrupt handling in basic operating mode................................................................ 24 7.1.4 basic mode timing ...................................................................................................... 25 7.1.5 register description .................................................................................................... 27 7.2 extended o perating mode ................................................................................... 29 7.2.1 state control ............................................................................................................ ... 31 7.2.2 configuration ............................................................................................................... 32 7.2.3 extended operat ing mode description........................................................................ 33 7.2.4 interrupt handling in extended operating mode ......................................................... 37 7.2.5 register summary....................................................................................................... 38 7.2.6 register descripti on ? control registers..................................................................... 38 7.2.7 register descripti on ? address registers ................................................................... 42 8 functional d escripti on ..................................................................... 45 8.1 introduction - frame format................................................................................. 45 8.1.1 phy protocol layer data unit (ppdu)........................................................................ 45
94 5131e-mcu wireless-02/09 at86rf230 8.1.2 mac protocol laye r data unit (mpdu)....................................................................... 46 8.2 frame check sequence (fcs) ............................................................................ 48 8.2.2 crc calc ulatio n.......................................................................................................... . 48 8.2.3 automatic fcs generat ion .......................................................................................... 49 8.2.4 automati c fcs check .................................................................................................. 49 8.2.5 register description .................................................................................................... 49 8.3 energy de tection (ed) ......................................................................................... 50 8.3.1 overview ................................................................................................................. .... 50 8.3.2 request an ed measurement ..................................................................................... 50 8.3.3 data interpretation...................................................................................................... . 51 8.3.4 register description .................................................................................................... 51 8.4 received signal streng th indicato r (rssi) .......................................................... 51 8.4.1 overview ................................................................................................................. .... 52 8.4.2 reading rssi............................................................................................................. . 52 8.4.3 data interpretation...................................................................................................... . 52 8.4.4 register description .................................................................................................... 52 8.5 link quality indication (lqi) ................................................................................. 53 8.5.1 overview ................................................................................................................. .... 53 8.5.2 request an lqi measurement .................................................................................... 53 8.5.3 data interpretation...................................................................................................... . 54 8.6 clear channel as sessment (cca)....................................................................... 54 8.6.1 overview ................................................................................................................. .... 54 8.6.2 cca configuration and request ................................................................................. 55 8.6.3 data interpretation...................................................................................................... . 55 8.6.4 register description .................................................................................................... 55 9 module d escription ........................................................................... 58 9.1 receiv er (rx) ....................................................................................................... 58 9.1.1 overview ................................................................................................................. .... 58 9.1.2 configuration ............................................................................................................... 58 9.2 transmit ter (tx) ................................................................................................... 58 9.2.1 overview ................................................................................................................. .... 58 9.2.2 configuration ............................................................................................................... 59 9.2.3 register description .................................................................................................... 59 9.3 frame buffer......................................................................................................... 60 9.3.1 frame buffer data ma nagem ent ................................................................................. 60 9.3.2 user accessible frame content .................................................................................. 60 9.3.3 frame buffer interrupt handling .................................................................................. 61 9.4 voltage regulator s (avreg, dvreg)................................................................ 62 9.4.1 overview ................................................................................................................. .... 62 9.4.2 configure the voltage regulators ............................................................................... 63 9.4.3 data interpretation...................................................................................................... . 63 9.4.4 register description .................................................................................................... 63 9.5 battery moni tor (batmon) .................................................................................. 64 9.5.1 overview ................................................................................................................. .... 64 9.5.2 data interpretation...................................................................................................... . 65 9.5.3 batmon interrupt handling........................................................................................ 65 9.5.4 register description .................................................................................................... 65 9.6 crystal osci llator (xosc)..................................................................................... 66
95 5131e-mcu wireless-02/09 at86rf230 9.6.1 overview ................................................................................................................. .... 67 9.6.2 integrated oscillator setup .......................................................................................... 67 9.6.3 external reference frequency setup.......................................................................... 68 9.6.4 master clock si gnal output (clkm)............................................................................ 68 9.6.5 register description .................................................................................................... 69 9.7 frequency synt hesizer (pll)............................................................................... 71 9.7.1 overview ................................................................................................................. .... 71 9.7.2 rf channel selection.................................................................................................. 71 9.7.3 calibration loops ........................................................................................................ 71 9.7.4 pll interrupt handling................................................................................................. 72 9.7.5 register description .................................................................................................... 72 9.8 automatic filt er tuning (ftn) .............................................................................. 74 10 radio transcei ver usage ............................................................... 75 10.1 frame receiv e procedure ................................................................................. 75 10.2 frame transm it procedure ................................................................................ 75 11 technical parame ters ..................................................................... 77 11.1 absolute ma ximum ratings................................................................................ 77 11.2 recommended op erating range ...................................................................... 77 11.3 digital pin specifications .................................................................................... 77 11.4 digital interface ti ming specifications ............................................................... 78 11.5 general rf specific ations.................................................................................. 78 11.6 transmitter specifications .................................................................................. 79 11.7 receiver s pecifications ...................................................................................... 79 11.8 current consumpt ion specifications .................................................................. 80 11.9 crystal parame ter requirements ....................................................................... 80 12 register refere nce ......................................................................... 81 abbreviat ions ....................................................................................... 83 13 ordering informat ion ...................................................................... 85 14 soldering in form ation..................................................................... 85 15 package thermal properties .......................................................... 85 16 package dra wing ? 32qn1 ............................................................. 86 appendix a - continuous tr ansmission t est m ode ......................... 87 a.1 - overview ............................................................................................................ 87 a.2 - config uration...................................................................................................... 87 a.3 - disc laimer .......................................................................................................... 88 appendix b - errata ............................................................................. 89 at86rf230 rev. b .................................................................................................... 89 at86rf230 rev. a .................................................................................................... 89 references............................................................................................ 91
96 5131e-mcu wireless-02/09 at86rf230 data sheet revi sion history ............................................................... 92 rev. 5131d-zigb-12/03/07........................................................................................ 92 rev. 5131c-zigb-05/22/07........................................................................................ 92 rev. 5131a-zigb-06/14/06........................................................................................ 92 table of contents ................................................................................. 93
97 5131e-mcu wireless-02/09 at86rf230
98 5131e-mcu wireless-02/09 at86rf230 disclaimer headquarters international atmel corporation 2325 orchard parkway san jose, ca 95131 usa tel: 1(408) 441-0311 fax: 1(408) 487-2600 atmel asia unit 1-5 & 16, 19/f bea tower, millennium city 5 418 kwun tong road kwun tong, kowloon hong kong tel: (852) 2245-6100 fax: (852) 2722-1369 product contact atmel europe le krebs 8, rue jean-pierre timbaud bp 309 78054 saint-quentin-en- yvelines cedex france tel: (33) 1-30-60-70-00 fax: (33) 1-30-60-71-11 atmel japan 9f, tonetsu shinkawa bldg. 1-24-8 shinkawa chuo-ku, tokyo 104-0033 japan tel: (81) 3-3523-3551 fax: (81) 3-3523-7581 web site www.atmel.com/ technical support avr@atmel.com sales contact www.atmel.com/contacts literature request www.atmel.com/literature disclaimer: the information in this document is provi ded in connection with atmel products. no license, express or imp lied, by estoppel or otherwise, to any intellectual property right is granted by this docum ent or in connection with the sale of atmel products. except a s s et forth in atmel? s terms and condition s of s ale located on atmel? s web s ite, atmel assume s no liability what soever and di s claims any expre ss , implied or s tatutory warranty relating to it s product s including, but not limited to, the implied warranty of merchantability, fitne ss for a particular purpo s e, or non-infringement. in no event s hall atmel be liable for any direct, indirect, con s equential, punitive, s pecial or incidental damage s (including, without limitation, damage s for lo ss of profit s, bus ine ss interruption, or lo ss of information) ari s ing out of the u s e or inability to u se thi s document, even if atmel ha s been advi s ed of the po ss ibility of such damage s. atmel makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and rese rves the right to make changes to specifications and product descriptions at any time without notice. atmel does not make any commitment to up date the information contained herein. unless specifically provided otherwise, at mel products are not suitable for, and shall not be used in, automotive applications. atme l?s products are not intended, authorized, or wa rranted for use as components in applications inte nded to support or sustain life. ? 2009 atmel corporation. all rights reserved . atmel?, atmel logo and combinations ther eof, avr? and others, are registered trademarks or trademarks of atmel corporation or its subsidiaries. other terms and produc t names may be trademarks of others.

▲Up To Search▲

Price & Availability of AT86RF230-ZU

	To Download AT86RF230-ZU Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .